Reference
Endpoint reference
The stable HTTP surface included in the starter.
Health
| Method | Path | Purpose |
|---|---|---|
GET | /healthz | Process liveness |
GET | /readyz | API database readiness |
Application API
| Method | Path |
|---|---|
POST | /api/v1/auth/register |
POST | /api/v1/auth/login |
POST | /api/v1/auth/logout |
GET | /api/v1/me |
GET | /api/v1/auth/providers |
GET | /api/v1/workspaces |
POST | /api/v1/workspaces |
POST | /api/v1/projects |
POST | /api/v1/session/selection |
GET | /api/v1/project-context |
GET, POST | /api/v1/projects/{project_id}/api-keys |
DELETE | /api/v1/api-keys/{api_key_id} |
All errors use { "error": { "code", "message", "request_id" } }. Never expose raw database or provider errors to clients.
The project-context endpoint accepts either the application's Session scheme or a project key:
curl http://localhost:4000/api/v1/project-context \
-H "Authorization: ApiKey sk_..."Random-number API
GET /api/v1/random-number requires Authorization: Bearer <access-token> with the configured MCP resource audience and project:read. It returns { "number": 42 }, where the number is an integer from 0 through 100. Application sessions and API keys are not accepted on this OAuth resource route.
OAuth and MCP
See Authentication for the authorization-server endpoints and MCP server for protected-resource discovery.