api3-primary-sources-2026-05-11

API3 primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://api3.org/
  • Official homepage
  • Used to anchor the current project identity and official entry point
• https://docs.api3.org/llms-full.txt
  • Official docs export
  • Used to confirm the live product framing around Api3 Market, OEV-based monetization, deviation-threshold and heartbeat plan parameters, first-party-source verification, dApp-specific proxy routing, and the claim that feeds are offered at estimated operating cost
• https://github.com/api3dao/api3-whitepaper
  • Official whitepaper repository
  • Used to anchor the original conceptual framing of dAPIs, first-party oracles, DAO governance, staking, and service-coverage design
• https://raw.githubusercontent.com/api3dao/api3-whitepaper/master/api3-whitepaper.tex
  • Whitepaper source
  • Used to quote the strongest mechanism claims directly from the canonical document
• https://github.com/api3dao/contracts
  • Official contracts repository
  • Used to confirm that the protocol surface includes data-feed contracts, OEV auction-related contracts, chain metadata, dApp registries, and deterministic proxy-address tooling
• https://raw.githubusercontent.com/api3dao/contracts/main/README.md
  • Contracts repository README
  • Used to confirm the market integration workflow, communal versus dApp-specific proxy-address computation, and the inclusion of OEV-auction functionality in the delivered contract package
• https://github.com/api3dao/airnode
  • Official Airnode repository
  • Used to anchor Airnode as a first-party oracle implementation component rather than treating it as a vague brand claim
• https://raw.githubusercontent.com/api3dao/airnode/master/packages/airnode-node/README.md
  • Airnode node README
  • Used to confirm that Airnode is the node layer connecting blockchains to the outside world and to inspect the functional split around authorization, request handling, verification, fulfillment, and heartbeat/reporting

Local copies saved

• api3-whitepaper.pdf

Notes

• API3 cleared the bar because it is not just another oracle brand; it makes source ownership and source certification first-class design choices rather than assuming that data providers and node operators are separate layers.
• The most useful reusable split is between source provenance and feed commercialization. Api3 does not only say “use our feeds”; it specifies how feeds are activated, how update policies are sold, how first-party status is audited, and how dApp-specific proxy addresses are derived.
• Airnode is a crucial lower layer. Without it, the first-party-oracle narrative would collapse into marketing. Keeping Airnode conceptually visible helps compare API3 against systems that rely on independent reporter sets, delegated operators, or middleware-heavy adapter stacks.
• The official contracts package exposes a quieter but important control surface: chain allowlists, dApp aliases, proxy-address computation, and metadata distribution. Those are practical governance and distribution levers even if the data sources themselves are first-party.
• The whitepaper’s older staking-and-service-coverage emphasis and the current docs’ stronger Market-plus-OEV emphasis are analytically useful together because they show how the project’s center of gravity has shifted from broad oracle-theory framing toward commercialization, provenance verification, and OEV-linked distribution.