Runtime=Agent Server
To build agentic products or an agent platform, you need to run your system as a horizontally scalable, durable service that is reachable over an API. That’s what a runtime gives you.
AgentOS turns the Agent(...) into a FastAPI app with persistent sessions, JWT-based authentication, observability, and interfaces for Slack, Telegram, and more.
What the runtime gives you
The runtime covers the ground between your agent code and a shipped service:| Concern | How AgentOS handles it |
|---|---|
| HTTP API | Auto-generated endpoints for every registered agent, team, and workflow |
| State | Sessions and memory persisted to your db |
| Streaming | SSE on every run endpoint; tokens and tool calls stream as they happen |
| Auth | JWT validation with RBAC scopes built-in |
| Scheduling | In-process cron that polls the database and fires due jobs |
| Observability | OpenTelemetry tracing into the same db, queryable with SQL |
| Interfaces | Slack, Telegram, WhatsApp, Discord, A2A, AG-UI |
| Human in the loop | Pause runs for user confirmation, admin approval, or external execution |
Agent(...) runs in a script, a test, or an AgentOS service. AgentOS itself is stateless: state lives in db, so you can scale horizontally to handle load.
AgentOS also runs teams and workflows, not only single agents. See Build a
Product.
What’s in this section
| Page | Covers |
|---|---|
| Serve as an API | The HTTP endpoints AgentOS generates and how to add your own |
| Storage | Database backends and what gets stored |
| Context | Knowledge, dependencies, and live context providers |
| Human Approval | Pausing runs for confirmation, approval, or external systems |
| Observability | Tracing, run history, audit logs |
| Security & Auth | JWT, RBAC scopes, request isolation |
| Interfaces | Slack, Telegram, WhatsApp, A2A, AG-UI |
| Scheduling | Cron jobs and multi-step workflows |
| Deploy | Docker, Railway, AWS, GCP, scaling |
| Build a Product | From a working AgentOS to a shipped product |