Portfolio API
API by Bo Kendell · rest
Portfolio oRPC + REST API Versioning and deprecation The version is in the URL path (/api/v1/...). A breaking change ships as a new path segment (/api/v2); anything additive lands in place. Nothing is removed silently. When an operation is scheduled for removal its responses start carrying a Deprecation header (draft-ietf-httpapi-deprecation-header) on the day the decision takes effect, and an RFC 8594 Sunset header once a removal date is committed — always at least 90 days out. Both are declared in components.headers, so an agent can watch for them mechanically rather than trusting this paragraph. Every 4xx and 5xx body is the Error schema: a machine-readable code, a human-readable message, and a data object repeating the code and HTTP status. Input-validation failures additionally carry raw Zod issues.
Endpoint: https://api.bokendell.com/
Verification: observed. Source: crawl.
Capabilities (30)
- Get combined portfolio activity
- Get GitHub contributions
- Get GitHub events
- Get latest authored commit
- Get LeetCode stats
- Get cached weekly commit summary
- Stream an AI chat response
- Homepage live-MCP demo (public no auth)
- /mcp/try multi-tool trace demo (public no auth)
- List AI chat tools (public registry)
- Send an email to Bo from the AI chat tool
- Create contact submission
- List timeline events
- Get event by id
- Health check
- List published posts
- Get a post by slug
- List profiles
- Get profile by id
- List projects
- List archive projects
- List featured projects
- Get project by slug
- Get the canonical resume read-model
- List social links