# Agno vs Strands Agents (slim)

> Strands Agents scores 80 (A) to Agno's 70.9 (BB) for agent frameworks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agno-vs-strands-agents.md (~4,000 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/agno-vs-strands-agents.json · canonical https://www.anchorterminal.com/compare/agno-vs-strands-agents
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Strands Agents scores 80 (A) on agent readiness against Agno's 70.9 (BB), and leads in 6 of 7 scored categories. Agno leads on transparency & trust. Both do agent frameworks.

- Agno: BB 70.9, rank #179 of 1510 · https://www.anchorterminal.com/tools/agno.min.md
- Strands Agents: A 80, rank #15 of 1510 · https://www.anchorterminal.com/tools/strands-agents.min.md
- Agno, good for Python teams that want agents, teams and workflows plus a self-hosted server with REST, MCP, approvals and scheduling in one package. Ahead on Transparency & trust, 84 against 72.
- Strands Agents, good for Python or TypeScript teams, especially on AWS, who want a model-driven loop with MCP, multi-agent patterns and approval gates. Ahead on Schema & documentation, 95 against 90; Agent ergonomics, 87 against 76; Security & auth, 89 against 64; Payments & pricing, 60 against 50. Also No key needed to call it.

| Category | Agno | Strands Agents |
| --- | --- | --- |
| Reliability (16%) | 83 | 87 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 95 |
| Agent ergonomics (13%) | 76 | 87 |
| Security & auth (14%) | 64 | 89 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 87 |
| Transparency & trust (7%) | 84 | 72 |

| Fact (where they differ) | Agno | Strands Agents |
| --- | --- | --- |
| Vendor | Agno Inc. | Amazon Web Services |
| Auth | API key | None |
| Last release | 2026-10-29 | 2026-11-04 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | 43k stars, 476k PyPI/wk | 9.1k stars, 698k npm/wk, 8.9M PyPI/wk |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Security & auth, Strands Agents +25: 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.); Strands Agents 89 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing). No usage analytics found in either SDK, and OpenTelemetry is opt-in (25). Interrupts and the harness's interventions gate tool calls behind human approval or Cedar policies, but the default sandbox is the local host (16). Guardrails, PII redaction and trusted message history pages, with Bedrock Guardrails integration (13). OpenTelemetry traces for every model and tool call (15). The AWS Vulnerability Disclosure Program on HackerOne and three advisories in October 2026 published with fixed versions (20). 25+16+13+15+20 = 89.)
- Transparency & trust, Agno +12: Agno 84 (Apache 2.0 (30). The telemetry page lists the fields sent and says identifiers are not hashed, and the pricing page says the control plane holds no copy of customer data. The terms and privacy pages render only with JavaScript and were not read, and no retention period for telemetry was found (15). Migration guides for 2.0 and 3.0 and migration notices on what was removed, with no written deprecation policy found (10). Telemetry is disclosed in the README and docs with an opt-out, though the environment variable does not cover AgentOS or evals (18).); Strands Agents 72 (Apache-2.0 (30). A library that stores session state where the developer configures it. The default FileSessionManager kept sessions world-readable in /tmp until 1.48.0, which the October advisories record and fix (20). A written deprecation policy with warnings and removal at majors, without a dated support window (16). Telemetry is opt-in and documented (20). 30+20+16+20 = 86.)
- Agent ergonomics, Strands Agents +11: 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).); Strands Agents 87 (Framework reading. An MCPClient is passed straight to the agent in a few lines and its lifecycle is managed, with tool filtering per client (22). Conversation managers, turn limits, token budgets and cancellation bound each run (20). Stop reasons and typed events, and hooks that can retry a model or tool call (16). Retry strategies, session managers that persist and resume a conversation, and interrupts that resume where they paused (17). Two official languages, but the default provider is Bedrock, which needs AWS credentials and model access (12). 22+20+16+17+12 = 87.)
- Payments & pricing, Strands Agents +10: Agno 50 (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).); Strands Agents 60 (Self-hosted rule. Free Apache-2.0 packages with nothing to buy from the project (20 + 20 + 20). No payment protocol (0). Model calls are paid to the provider. 0+20+20+20 = 60.)
- Schema & documentation, Strands Agents +5: 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.); Strands Agents 95 (Framework reading. Typed Python and TypeScript APIs with a reference for each (25). llms.txt with a Markdown twin of every page (10). The llms.txt and docs say when to use Strands over a hand-written loop and when to take the harness rather than the SDK (18). Tools are typed from decorated functions or Zod schemas (15). Python and TypeScript examples on every page, stop reasons and hook events documented, with no catalogue of exceptions (12). Versioning page and tagged releases per package (15). 25+10+18+15+12+15 = 95.)