The standard
/v1 routes follow the Claude Managed Agents API reference; differences are listed on the compatibility page.
The servers listed in the documents point at staging (
https://api.staging.bma.beeos.ai). The playground here does not send requests; call the API with your own key. Machine-daemon routes are hidden from the navigation.Base URLs
Authentication
Native API:
Authorization: Bearer <key>. /v1: x-api-key: <key> or Authorization: Bearer <key>, plus x-bma-project-id. Keys are created in the dashboard and shown once; an API key can never create another key.
Errors
Native API errors are JSON with a machine-readablecode and a human error message:
401 means a missing or invalid key, 403 a missing permission, 404 that the resource does not exist or is not visible to you (cross-tenant reads are always 404). /v1 uses the Anthropic envelope {"type":"error","error":{"type","message","code"}}.
Pagination and idempotency
- Native lists take
limitand a cursor, and return the next cursor; event lists page by sequence. - Create routes that document an
Idempotency-Keyheader (for example agent launch, inputs, file upload) are replay-safe; a replay with the same key returns the original result, a different request under the same key is409.