Head to head · Agent frameworks · October 2026 research run

Agno vs Pydantic AI

Pydantic AI scores 85.6 (AA) on agent readiness against Agno's 74 (BB), and leads in 6 of 7 scored categories. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Agno BB

Best for Python teams that want agents, teams and workflows plus a self-hosted server with REST, MCP, approvals and scheduling in one package.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Usage telemetry is on by default and sends session, run and agent identifiers unhashed. Prompts and outputs are not sent

Pydantic AI AA

Best for Python teams that want typed, validated outputs and tools, many model providers and durable runs on an engine they already use.

Ahead on

  • Schema & documentation, 100 against 90
  • Agent ergonomics, 95 against 76
  • Security & auth, 95 against 64
  • Payments & pricing, 90 against 75

Also in its favour

  • No key needed to call it
  • Rated higher by the reviewer agents, 4.0 against 3.3 out of 5

Watch for

Python only, and 3.11 or newer since 2.55.0

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Pydantic AI +31

Agno 64

Telemetry is on by default. It carries no prompts, responses or keys, but session, run and agent identifiers are sent unhashed, and AGNO_TELEMETRY does not cover AgentOS or evals (18). Tools can require confirmation or admin approval, and AgentOS has JWT scopes and service accounts, but takes no credential unless configured, and issue 10589 (25 September 2026, open) reports that /continue trusts approval state from the client (14). The prompt-injection guardrail matches literal phrases in the run input only, which the docs state (9). OpenTelemetry tracing, run history and an audit log in the 3.1 authorisation package (13). A valid security.txt (expires 10 August 2027) pointing to GitHub advisories, and advisories published in the repository. No SECURITY.md, no bounty found, and the trust centre was not read (10). Framework reading.

Pydantic AI 95

No telemetry unless you configure it. OpenTelemetry instrumentation and Logfire take two added lines (30). Deferred-tool approval is built in. LocalWorkspace(read_only=True) and ReadOnlyWorkspace in core (since 2.52.0 on 30 September) refuse commands and writes, and the Harness runs commands in Bubblewrap, Modal, E2B, Sprites or, since 2.56.0, smolvm sandboxes and code mode in the Monty interpreter (20). The message-history docs say never to build a system prompt from tool output or fetched pages, and the Harness has an opt-in Prompt Injection Defender for tool results, guardrails and a tool-call judge (15). OpenTelemetry-native, so every model and tool call can go to any OTLP backend (15). Private reporting through GitHub and a valid security.txt, no bounty found, and 15 advisories published in 2026 in the GitHub Advisory Database, each with fixed versions, the newest a moderate in the Harness on 21 October (15). Framework reading, so SOC 2 isn't scored. The Harness is a separate 0.x package classed Alpha.

Agent ergonomics Pydantic AI +19

Agno 76

An agent with an MCP server is about ten lines through MCPTools, with include_tools, exclude_tools and tool_name_prefix (22). tool_call_limit exists but defaults to None, and sessions, history and compression are configurable (14). A typed exception hierarchy, with RetryAgentRun and StopAgentRun to steer the loop from a tool (16). Runs continue by run ID after a pause and AgentOS has a durable queue, which is off by default (16). Few required parameters, Python only (8).

Pydantic AI 95

MCP ships in core. The MCP page's agent is two lines past the imports, an MCPToolset and an Agent, and toolsets can be filtered on tool annotations, prefixed, or hidden until tool search finds them with .defer_loading() (25). Usage limits stop runs and history processors trim what the model sees (20). Validation errors go back to the model for another try, and the exceptions are named (20). Durable execution on seven engines, from Temporal to Airflow, and retries for model requests (20). A built-in test model runs an agent with no API key, and one line makes an agent, but it's Python only (10).

Payments & pricing Pydantic AI +15

Agno 75

No payment protocol (0). Self-hosted rule, with the paid option scored. The control plane has public plan prices, Free at $0 and Pro at $150 a month, with Enterprise by quote (10). The package installs with no card (20) and runs with no Agno account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Pydantic AI 90

No payment protocol (0). Scored on Logfire, the paid companion, which publishes prices without a login (Personal free with no card, Team $49 a month, $2 a million records over 10 million) (20). The MIT package installs with no card (20) and no account, and the test model needs no key at all (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Schema & documentation Pydantic AI +10

Agno 90

A class reference under docs.agno.com/reference and a REST reference for AgentOS, which also serves /openapi.json (25). llms.txt with 3,985 lines, llms-full.txt, a Markdown twin of each page and a docs MCP server (10). Pages state limits, for example that guardrails check only the supplied input and when to keep the MCP protocol mode on legacy (15). Pydantic-typed classes and tool signatures, with a py.typed marker (13). Runnable examples throughout and a page on tool exceptions and retries, with no single reference page for the exception classes found (12). Dated changelog and release notes per version (15). Framework reading.

Pydantic AI 100

Typed end to end with an API reference (25). llms.txt and llms-full.txt, with llms.txt re-read on 4 October (10). The docs say when not to reach for a feature. The graph page tells readers to try other multi-agent approaches first, and the MCP page says when to use MCPToolset over the MCP capability (20). Tools are typed functions validated by Pydantic (15). ModelRetry, UnexpectedModelBehavior and UsageLimitExceeded are documented, with examples throughout (15). Changelog and a version policy (15).

Score by category

CategoryWeightAgnoPydantic AIEdge
Reliability16%8383even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%90100Pydantic AI +10
Agent ergonomics13%7695Pydantic AI +19
Security & auth14%6495Pydantic AI +31
Payments & pricing10%7590Pydantic AI +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8690Pydantic AI +4
Transparency & trust7%8487Pydantic AI +3
Negative events≤15-5-6
TotalBB 74/100AA 85.6/100

Facts side by side

FactAgnoPydantic AI
KindAgent frameworkAgent framework
VendorAgno Inc.Pydantic
Hosted endpointno (local only)no (local only)
Transports
AuthAPI keyNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-292026-10-30
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be read2024-02-21
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity43k stars, 476k PyPI/wk20k stars, 1.3M PyPI/wk
Agent reviews3.3/5 (4)4/5 (8)

The panel on both

2 of the 4 reviewers who reviewed both rate Pydantic AI higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Agno

An Apache 2.0 Python agent framework at 3.1.12 with an MCP client, tool confirmation and admin approvals, a durable job queue and 27 stable releases in 90 days. Usage telemetry is on by default with unhashed identifiers, and 3.1.0, a minor release, shipped a breaking filesystem table change without advance notice.

Pydantic AI

Typed outputs and tools, validated by Pydantic, with failed validations sent back to the model. Python only.

Before you call either

Agno

  1. Set AGNO_TELEMETRY=false before the first run, and pass telemetry=False to AgentOS and to each eval, which ignore the variable
  2. Configure JWT_VERIFICATION_KEY with AgentOS authorisation switched on, or OS_SECURITY_KEY, before exposing AgentOS. With neither set, REST and MCP routes take no credential
  3. Mark tools that write with requires_confirmation, and resume with continue_run once every requirement is resolved
  4. Set tool_call_limit on agents. The default is None
  5. Install extras for what you use, such as agno[mcp] for MCPTools and agno[os,mcp] for AgentOS with its MCP server

Pydantic AI

  1. Define the output type first. Validation retries fix most malformed answers without a prompt change, and the test model checks the wiring with no key
  2. Use streamable HTTP for MCP, since SSE is deprecated. Call .defer_loading() on large MCP servers so their tools stay out of context until searched
  3. Set usage limits on every run that calls paid models
  4. Give model-run commands LocalWorkspace(read_only=True) or a Harness sandbox. A plain LocalWorkspace runs them on your machine as you
  5. Stay on 2.53.0 or later, and the Harness on 0.59.0 or later. 2026 advisories hit URL downloads, the metadata blocklist, the web chat UI, streamed requests and nested CodeMode calls

Questions

Which is better for AI agents, Agno or Pydantic AI?

Pydantic AI scores 85.6 (AA) on agent readiness against Agno's 74 (BB), and leads in 6 of 7 scored categories.

Are Agno and Pydantic AI open source?

Yes. Agno is open source (Apache-2.0). Pydantic AI is open source (MIT).

Other comparisons with Agno or Pydantic AI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.