Agno
Agno (formerly Phidata) is a high-performance open-source Python framework for building multi-modal, multi-agent systems with memory, knowledge, tools, and reasoning capabilities. It provides both an agent development SDK and AgentOS, a production runtime that transforms agents into managed APIs with 50+ endpoints for runs, sessions, memory, knowledge, traces, evaluations, and scheduling. AgentOS supports RBAC, per-user session isolation, streaming via Server-Sent Events, background execution, and human-in-the-loop approval flows. The platform supports 30+ LLM providers and can be deployed on AWS, GCP, Railway, or air-gapped environments with data remaining in the customer's cloud.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Agno the way a machine reads it — 71 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Agno scores 48.5/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Agno's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/agno/"
title="Agno on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agno.svg"
alt="Agno Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/agno/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/agno/"
title="Agno on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agno/card.svg"
alt="Agno Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Agno
Each block below is one kind of artifact we hold for Agno. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Agno A2A API
The A2A API from Agno — 15 operation(s) for a2a.
Agno Agents API
The Agents API from Agno — 6 operation(s) for agents.
Agno AGUI API
The AGUI API from Agno — 2 operation(s) for agui.
Agno Approvals API
The Approvals API from Agno — 5 operation(s) for approvals.
Agno Components API
The Components API from Agno — 6 operation(s) for components.
Agno Core API
The Core API from Agno — 2 operation(s) for core.
Agno Database API
The Database API from Agno — 2 operation(s) for database.
Agno Evals API
The Evals API from Agno — 2 operation(s) for evals.
Agno Health API
The Health API from Agno — 1 operation(s) for health.
Agno Home API
The Home API from Agno — 1 operation(s) for home.
Agno Knowledge API
The Knowledge API from Agno — 8 operation(s) for knowledge.
Agno Memory API
The Memory API from Agno — 5 operation(s) for memory.
Agno Metrics API
The Metrics API from Agno — 2 operation(s) for metrics.
Agno Registry API
The Registry API from Agno — 1 operation(s) for registry.
Agno Schedules API
The Schedules API from Agno — 7 operation(s) for schedules.
Agno Sessions API
The Sessions API from Agno — 5 operation(s) for sessions.
Agno Slack API
The Slack API from Agno — 2 operation(s) for slack.
Agno Teams API
The Teams API from Agno — 5 operation(s) for teams.
Agno Traces API
The Traces API from Agno — 5 operation(s) for traces.
Agno Whatsapp API
The Whatsapp API from Agno — 2 operation(s) for whatsapp.
Agno Workflows API
The Workflows API from Agno — 5 operation(s) for workflows.
Agno Agents API
Run and manage individual agents.
Agno Evals API
Evaluation runs for quality and reliability.
Agno Knowledge API
Knowledge base content used for retrieval.
Agno Memory API
Persistent per-user memories.
Agno Sessions API
Conversation history and state for agents, teams, and workflows.
Agno Teams API
Run and manage teams of agents.
Agno Workflows API
Run and manage multi-step workflows.
Scroll within the panel for all 28 ·
Open Collections 22
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAgno API Reference A2A API
OPEN COLLECTIONAgno API Reference A2A Agents API
OPEN COLLECTIONAgno API Reference A2A AGUI API
OPEN COLLECTIONAgno API Reference A2A Approvals API
OPEN COLLECTIONAgno API Reference A2A Components API
OPEN COLLECTIONAgno API Reference A2A Core API
OPEN COLLECTIONAgno API Reference A2A Database API
OPEN COLLECTIONAgno API Reference A2A Evals API
OPEN COLLECTIONAgno API Reference A2A Health API
OPEN COLLECTIONAgno API Reference A2A Home API
OPEN COLLECTIONAgno API Reference A2A Knowledge API
OPEN COLLECTIONAgno API Reference A2A Memory API
OPEN COLLECTIONAgno API Reference A2A Metrics API
OPEN COLLECTIONAgno API Reference A2A Registry API
OPEN COLLECTIONAgno API Reference A2A Schedules API
OPEN COLLECTIONAgno API Reference A2A Sessions API
OPEN COLLECTIONAgno API Reference A2A Slack API
OPEN COLLECTIONAgno API Reference A2A Teams API
OPEN COLLECTIONAgno API Reference A2A Traces API
OPEN COLLECTIONAgno API Reference A2A Whatsapp API
OPEN COLLECTIONAgno API Reference A2A Workflows API
OPEN COLLECTIONScroll within the panel for all 22 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Agno Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Agno Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Agno Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Agno Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Agno API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AgentResponse
JSON SCHEMAAgentSessionDetailSchema
JSON SCHEMAApprovalResponse
JSON SCHEMAComponentResponse
JSON SCHEMAHealthResponse
JSON SCHEMAKnowledgeDomainConfig
JSON SCHEMAMetricsResponse
JSON SCHEMARunSchema
JSON SCHEMAScheduleResponse
JSON SCHEMASessionSchema
JSON SCHEMATraceDetail
JSON SCHEMAUserMemorySchema
JSON SCHEMAScroll within the panel for all 12 ·
Examples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Agno Agentos Api Examples
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Agno — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/agno · machine-readable index on apis.io
This is an independent, third-party profile of Agno, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.