Skip to main content
Application engineers use the AgentOS API to embed agents in products and manage runtime state from any HTTP client.
The response includes the run output, run_id, and session_id. Reuse the same session_id to group later runs in the same thread. Configure chat history when the model needs messages from earlier runs. Teams and workflows use the same run pattern:

Discover an Instance

GET /info returns the metadata a client needs before making authenticated calls. The endpoint is public.
Use GET /config to retrieve component IDs, database IDs, interfaces, and domain configuration. Send credentials when auth_mode requires them.

API Surfaces

See the API reference for every path and schema.

Stream Run Events

Run endpoints stream Server-Sent Events by default. Use curl -N to print events as they arrive:
Set stream=false when the caller needs one JSON response after the run completes.

Pass Runtime Context

Run endpoints accept JSON-encoded form fields alongside the message:

Authenticate Requests

Read auth_mode from GET /info, then send the matching credential:
Service-account tokens beginning with agno_pat_ are bearer credentials for machine callers. They are available when the AgentOS instance has a database.

REST or Python Client

Next Steps