Public API documentation for people and AI agents.
Read how RunAgencyOS authentication works, create scoped workspace API keys inside your account, and connect compatible MCP clients. The documentation is public. Calling the API still requires credentials you create after signing in.
Same origin as the product.
Production lives at https://runagencyos.com. Browser and server clients call relative paths under /api/v1/... and /mcp/ on that host.
https://runagencyos.com/api/v1/... https://runagencyos.com/mcp/ https://runagencyos.com/healthz
Two credential models. Both stay private to your account.
RunAgencyOS does not expose an anonymous write API. Documentation can be shared freely; credentials cannot.
Web app and REST (JWT)
The signed-in product uses short-lived access JWTs from login or refresh. Most /api/v1/* routes expect Authorization: Bearer <access_token> plus the workspace header when a tenant context is required. Workspace API keys are not a general REST gateway today.
MCP and agents (API keys)
Owners and admins create scoped workspace API keys in Settings → API Keys & MCP. Keys look like af_..., are shown once, and authenticate the streamable HTTP MCP endpoint with Authorization: Bearer af_.... Scopes: read, write, and optional unattended for trusted automations.
Gap to know: REST routes are still JWT-session oriented. If you need a pure machine REST client without a browser login, use MCP tools today or plan a follow-up that accepts workspace API keys on selected REST routes.
Native MCP tools over HTTPS.
Point Claude Code or any streamable-HTTP MCP client at the workspace endpoint. Keep the trailing slash so the bearer key never rides a redirect.
claude mcp add --transport http runagencyos https://runagencyos.com/mcp/ \ --header "Authorization: Bearer <YOUR_API_KEY>"
Machine-readable copies for agents and bots.
Hand these URLs to an assistant when you want it to understand how to talk to RunAgencyOS. They describe the surface; they do not unlock your data.
Create a workspace, then create a key.
Documentation is public. API access starts inside your RunAgencyOS account.
No card required to start.