We build our agents, teams, and workflows with the Agno SDK and take them live using AgentOS. What does it mean to take an agent live? We should be able to:Documentation Index
Fetch the complete documentation index at: https://docs.agno.com/llms.txt
Use this file to discover all available pages before exploring further.
- Run the agent on demand, via an API request, or via interfaces like Slack, Telegram, and others.
- Maintain long-running sessions that last from minutes to days to weeks.
- Be durable across restarts, replicas, and infrastructure failures.
- Be secure against unauthenticated access.
- Monitor every run and action taken.
What the runtime gives you
The runtime covers the ground between your agent code and a production service:| Concern | How AgentOS handles it |
|---|---|
| HTTP API | Auto-generated endpoints for every registered agent, team, and workflow |
| Persistence | 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, A2A, AG-UI |
| Human in the loop | Pause runs for user confirmation, admin approval, or external execution |
Explore
Agent API
Run your agent platform as an API.
Agent Storage
Add durability and persistence.
Observability
Tracing, run history, and audit logs in your own database.
Security and Auth
JWT validation, RBAC scopes, and per-request isolation.
Scheduling
In-process cron and multi-step workflows.