What you can do with BeeOS
Deploy agents
Launch an agent instance on managed infrastructure with one API call.
Invoke agents
Send messages — synchronous, streaming, or async tasks — over the
OpenAPI surface.
A2A protocol
Enable agents to discover and collaborate over the JSON-RPC
Agent-to-Agent protocol.
MCP integration
Expose agent skills as MCP tools for Claude, ChatGPT, Cursor, and
other model-context-protocol clients.
Webhooks & files
Receive terminal-state callbacks with HMAC signing; share files via
presigned URLs.
Choosing a protocol
Decide between OpenAPI, A2A, and MCP for your integration.
The four public hosts
BeeOS exposes four independent public surfaces. Each has its own host, its own preferred credential, and its own contract — you pick the surface that matches your role.| Surface | Host | Audience | Auth | Use case |
|---|---|---|---|---|
| OpenAPI | openapi.beeos.ai | App owners, SDK users | JWT or oag_ User API Key | Catalog, deploy, instance lifecycle, agents listing & invoke, tasks, conversations, webhooks, files |
| A2A | a2a.beeos.ai | External agents | bak_ Agent API Key (User JWT fallback for owners) | Agent-to-Agent JSON-RPC tasks, agent card resolution, optional REST invoke |
| MCP | mcp.beeos.ai | AI clients (Claude, Cursor…) | OAuth 2.1 + PKCE, or bak_, or oag_ | Tool discovery and invocation per agent |
| Agent Gateway | agent.beeos.ai | Agent pods (you don’t call this directly) | Ed25519-signed agent identity | Agents call inward for file presign, messaging tokens, A2A |
Architecture at a glance
Where to start
Quickstart
Deploy your first agent and invoke it in under 5 minutes.
Authentication
oag_, bak_, OAuth, scopes, rotation.Calling agents
Idempotency, attachments, tasks, conversations.
Error reference
Every
error.code and the recovery hint.