# Agno
> Agno is an agent platform for customer-facing and internal agents. Build agents, teams and workflows with the Agno SDK, run them on AgentOS in your own infrastructure, and manage them from the Control Plane. Serve agents through your product over REST and through MCP clients.
Use this index to choose what to read. Follow the linked indexes rather than guessing page URLs. Summaries help select a source; consult the linked page for details and the documentation for version-specific APIs.
To set up Agno or build a new agent, start with [Set up Agno](https://www.agno.com/start.md).
To serve agents you already have, see [Run existing agents](https://www.agno.com/run-existing-agents.md).
For a specific use case, choose its Build guide below. Product pages explain the components.
## Build
- [Set up Agno and build your first agent](https://www.agno.com/start.md): Type: Build. Choose a deployment target, run the shared setup prompt, and verify your first agent.
- [Build a docs agent](https://www.agno.com/build/docs-agent.md): Type: Build. Build an assistant grounded in your documentation and serve it over MCP.
- [Serve agents to your end users](https://www.agno.com/build/end-user-management.md): Type: Build. Plan identity, per-user data isolation, roles and authorization for a customer-facing agent.
- [Put an agent in your product](https://www.agno.com/build/in-product-agent.md): Type: Build. Connect an agent to your application with authenticated sessions, streaming and controlled actions.
- [Run agents you already have](https://www.agno.com/run-existing-agents.md): Type: Build. Evaluate serving existing agents on AgentOS before deciding whether to port their implementation.
## Learn
- [Agno SDK](https://www.agno.com/products/sdk.md): Type: Conceptual. Python primitives for agents, teams and workflows, with tools, knowledge and memory.
- [AgentOS runtime](https://www.agno.com/products/runtime.md): Type: Conceptual. Serve agents as an API in your own infrastructure and operate their sessions and runs.
- [Control Plane](https://www.agno.com/products/control-plane.md): Type: Conceptual. Manage agents, inspect sessions and traces, and review approvals and evaluations.
## Choosing and comparing
- [Compare agent frameworks](https://www.agno.com/compare.md): Type: Comparison. Find a comparison, including strengths, tradeoffs and sources.
- [Agno vs LangGraph](https://www.agno.com/compare/agno-vs-langgraph.md): Type: Comparison. Compare capabilities and when to choose each; source review dated 2026-08-10.
- [Agno vs CrewAI](https://www.agno.com/compare/agno-vs-crewai.md): Type: Comparison. Compare capabilities and when to choose each; source review dated 2026-08-10.
- [Agno vs OpenAI Agents SDK](https://www.agno.com/compare/agno-vs-openai-agents-sdk.md): Type: Comparison. Compare capabilities and when to choose each; source review dated 2026-08-10.
## Pricing and enterprise
- [Pricing](https://www.agno.com/pricing.md): Type: Reference. Free, Pro and Enterprise plans, included capabilities and add-ons.
- [Enterprise](https://www.agno.com/enterprise.md): Type: Reference. Enterprise deployment, governance, support and contact information.
## Evidence
- [Benchmarks](https://www.agno.com/benchmarks.md): Type: Reference. Agent instantiation time and memory, with hardware, versions, measurement date and reproduction harness.
- [Customers](https://www.agno.com/customers.md): Type: Reference. Production deployments, attributed customer accounts and linked case studies.
- [Engineering blog](https://www.agno.com/blog.md): Type: Reference. Full index of engineering guides and case studies, with publication dates.
## Documentation and reference
- [Canonical names and naming history](https://www.agno.com/taxonomy.json): Type: Reference. Canonical product names, aliases, historical names such as Phidata, and sourced deprecations with replacements.
- [Documentation index](https://docs.agno.com/llms.txt): Type: Reference. SDK and AgentOS guides, examples and API reference; consult for implementation details.
- [Docs MCP server](https://docs.agno.com/mcp): Type: Reference. Query the Agno documentation from a coding agent that supports MCP.
- [Source code and cookbook](https://github.com/agno-agi/agno): Type: Reference. Agno source, working examples and release history.
- [Changelog](https://www.agno.com/changelog.md): Type: Changelog. Dated feature and fix entries, with release versions where available.
## Optional
- [Full page index](https://www.agno.com/sitemap.md): Type: Reference. Every listed page, build guide and published article, with type and summary.
- [About](https://www.agno.com/about.md): Type: Conceptual. The team behind Agno.
- [Community](https://www.agno.com/community.md): Type: Reference. Community support and places to participate.
- [Full site content for LLMs](https://www.agno.com/llms-full.txt): Type: Reference. An expanded content export; use the page index for targeted retrieval.
Measured from the saved file
Linked document
UTF-8 text size
4.9 KB4989 bytes
Token count
1140o200k_base encoding
Markdown links
2826 distinct URLs
Fenced code blocks
056 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
Agno
Opening blockquote
Agno is an agent platform for customer-facing and internal agents. Build agents, teams and workflows with the Agno SDK, run them on AgentOS in your own infrastructure, and manage them from the Control Plane. Serve agents through your product over REST and through MCP clients.
Context architecture
How the content is divided
7 H2 sections organize 28 parsed Markdown links. 23 links point to .md or .markdown paths; 3 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
BuildLine 11
5
905
199
LearnLine 19
3
492
110
Choosing and comparingLine 25
4
666
179
Pricing and enterpriseLine 32
2
269
60
EvidenceLine 37
3
465
99
Documentation and referenceLine 43
5
771
179
OptionalLine 51 · Optional
4
499
123
Nested indexes
1 distinct links point to other llms.txt paths. These are routes to more indexes, not proof their contents were included in this file.
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
1 H2 section named “Optional” contain 4 parsed links. 24 links sit outside those sections. That puts 14.3% of the file’s parsed links under Optional.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
MCP-related text was detected in the captured file. 1 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
Linked release and migration material
1 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.