API3
API3 is a first-party blockchain oracle network that connects real-world APIs directly to smart contracts without intermediary nodes. Its core technology is Airnode, a serverless oracle node that API providers operate themselves, cryptographically signing data before serving it on-chain. The API3 Market enables dApp developers to subscribe to managed decentralized APIs (dAPIs) — aggregated, multi-source data feeds covering 150+ price pairs across 40+ EVM chains — without speaking to a sales rep or signing a contract. API3's OEV (Oracle Extractable Value) mechanism captures MEV that traditionally leaks to bots around oracle updates and redistributes 80% of that revenue to the dApps reading the feeds, creating a net-positive oracle revenue model. The DAO governs the network via staked API3 tokens.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles API3 the way a machine reads it — 13 machine-readable artifacts across 6 APIs, 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 — API3 scores 43.7/100 (thin), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile API3
Each block below is one kind of artifact we hold for API3. 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 6
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.
API3 dAPI Data Feeds
Managed decentralized API (dAPI) data feeds sourced directly from first-party oracle nodes operated by the data providers themselves. Each feed aggregates signed data from multi...
API3 OEV Rewards
Oracle Extractable Value (OEV) Rewards is API3's revenue-sharing mechanism for dApps that integrate OEV-enabled Api3ReaderProxyV1 proxy contracts. When liquidation or arbitrage ...
API3 Airnode HTTP Gateway
The Airnode HTTP gateway exposes a REST endpoint that allows authorized callers to query an Airnode operator's API data off-chain without sending a blockchain transaction. API p...
API3 Airnodes API
Airnode address discovery
API3 Signed Data API
Reading and writing cryptographically signed oracle data
API3 Status API
Health and deployment information
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Api3 Plans
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.
Api3 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.
Api3 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.
Api3 Context
JSON-LDSecurity 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 API3 — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/api3 · machine-readable index on apis.io