Skip to main content
This guide walks you from zero to a running agent that you can chat with via the BeeOS public OpenAPI. The same flow works against http://localhost:8095 for local dev or https://openapi.beeos.ai for production.

Prerequisites

  • A BeeOS account at beeos.ai.
  • A User API Key (oag_...) from Settings → API Keys. The key acts as a long-lived bearer credential bound to your user — see Authentication for the credential format and rotation guidance.

1. Install the SDK

The published @beeos-ai/sdk is auto-generated from the OpenAPI contract using OpenAPI Generator (typescript-fetch). It exposes a Configuration value plus one class per OpenAPI tag — DeployApi, InstancesApi, AgentsApi, TasksApi, ConversationsApi, FilesApi. There is no BeeOS umbrella client.

2. Configure the client

Python users should install beeos, the stable official entry point. The complete generated OpenAPI surface remains available as beeos.sdk; see the Python SDK guide.

3. List the deploy catalog

4. Deploy an agent instance

Provisioning takes a few seconds. Poll GET /instances/{id} until status === "running", or watch the dashboard.

5. Find the agent ID

A deployed instance hosts one or more agents. The agent ID is what you invoke against (an instance can be replaced without breaking your integration; the agent identity is stable).

6. Invoke the agent

The blocking call returns a single JSON payload once the agent finishes its reply. For long prompts, see Streaming.

Streaming variant

Set Accept: text/event-stream on the same endpoint to receive agent_reply_delta chunks followed by a single agent_reply close frame. The SDK does not abstract SSE — drop to fetch / http.Client.

6.5. Where does the invoke show up?

Each invoke creates a short-lived protocol=openapi task channel, not a conversation. List it with:
GET /agents/{agentId}/conversations returns only long-lived dialog channels you opened explicitly with POST /conversations. If that list is empty right after an invoke, that is expected — see the calling agents guide for when to pick conversation vs invoke.

7. Clean up

Where to go next

Choosing a protocol

Decide between OpenAPI (this guide), A2A, and MCP.

Calling agents

Idempotency, attachments, tasks, conversations, error handling.

Webhooks

HMAC-signed terminal-state callbacks with retry + audit log.

A2A protocol

JSON-RPC + agent cards on a2a.beeos.ai.