API3: Decentralized APIs for Web3.0 (v1.0.3)

Last updated: October 8, 2026.

Original paper Original paper
Directories Ethereum Whitepapers & Research

API3’s Decentralized APIs for Web3.0 proposes connecting API businesses to blockchains through first-party oracles: the data provider operates the oracle service itself. This page explains the historical paper and distinguishes it from today’s feed, OEV and QRNG documentation. [1]

Document Decentralized APIs for Web3.0, v1.0.3, 40 PDF pages
Cover authors Burak Benligiray, Saša Milić and Heikki Vänttinen
Publication history Original v1.0.0: September 2020. Reviewed v1.0.3: June 2022, credited in the revision appendix to Erich Dylus and Burak Benligiray.
Scope First-party oracle architecture, DAO governance and proposed service coverage
Reuse license No explicit reuse license identified for the PDF. Airnode software separately uses MIT.

Why first-party data?

The paper argues that intermediary oracle operators add costs and dependencies between API providers and applications. Its alternative uses Airnode and DAO coordination, with staking intended to align governance and financial responsibility. Identifying a signer helps attribute data to a provider; it does not prove that a reported market price or real-world observation is correct. [1]

Current Market documentation makes first-party verification concrete: check that the operator runs an independent API business, certifies its signing key and makes its signed data available directly. Source identity and source independence require separate attention: many signatures do not necessarily represent many independent observations. [4]

Airnode and dAPIs

Airnode connects configured API operations to blockchain requests. Its repository describes serverless deployment and also provides Docker packages. Configuration, API credentials, infrastructure and gas funding still matter; “serverless” does not mean every API can operate without setup or maintenance. The repository’s MIT license applies to its software rather than automatically licensing the paper. [2] [3]

In current feed contracts, a beacon identifies a provider address and endpoint template. A beacon set aggregates constituent feeds; a dAPI maps a readable name to a feed ID. Providers sign observations, Signed APIs expose them off-chain, and Airseeker submits push updates. Anyone holding valid signed data can update a base beacon. Relaying remains part of delivery even though a relayer cannot substitute an arbitrary unsigned observation. [5]

Updates use deviation thresholds and heartbeat intervals. A threshold triggers an update after it is exceeded; it is not a hard bound on price error during a fast market move. Applications must handle stale values, and purchased update plans expire unless renewed. [4]

Governance and proposed service coverage

The paper links DAO staking to governance and a collateral pool for qualifying losses. Its coverage design includes agreed limits, premiums, evidence, claims and dispute resolution. It does not promise every user reimbursement, unlimited reserves or an infallible feed. A historical proposal is not evidence that a particular application presently has an active coverage policy. [1]

Later development: oracle extractable value

Oracle extractable value (OEV) concerns opportunities exposed by oracle updates, such as liquidations and arbitrage. Current documentation describes private auctions through partnered searchers using non-delayed data, alongside public Signed API searching on delayed data. Revenue allocation depends on the arrangement; API3-curated markets allocate OEV to API3. [7]

An OEV reader proxy selects the fresher base or application-specific OEV feed. The data-feed guide currently restricts OEV updates to partnered searchers. This permission is distinct from permissionless base-feed updates and from publicly observing delayed signed data. These mechanisms are later product context, not features to attribute wholesale to the 2020 paper. [5]

Security and operational limits

The current security guide identifies upgradeable reader proxies controlled by a 4-of-8 technical-team multisignature and source-configuration approvals by a 4-of-4 multisignature. Funding update wallets and maintaining infrastructure remain operational dependencies. It also describes an artificial base-feed delay of 0–15 seconds in the OEV design. These documented controls and latency tradeoffs should be evaluated for each integration. [6]

Provider signatures authenticate messages, not economic truth. A compromised source, unsuitable aggregation, stale data, contract bug or poorly handled outage can still affect an application. First-party provenance alone should not be treated as a guarantee of price accuracy or complete decentralization. [4] [6]

QRNG is a separate application

Legacy QRNG documentation describes AirnodeRrpV0 requests followed by a callback carrying the result. It lists quantum providers, while a testnet provider emulates the service using pseudorandom numbers. A quantum source does not remove provider, delivery or application-validation assumptions. The documented service has no subscription fee, but requesters still pay fulfillment gas. These legacy references explain the application; they do not certify current deployments or every network’s availability. [8] [9]

Social Media Sentiment

Not applicable to this historical technical-document summary. Project or token sentiment has not been inferred from the paper or promotional claims.

Last updated: 2026-10

Related Terms

See Also

Sources

  1. API3, Decentralized APIs for Web3.0, v1.0.3 — Official paper; checked October 8, 2026.
  2. Airnode repository: deployment and API integration overview — Official documentation or code; checked October 8, 2026.
  3. Airnode software license: MIT — Official documentation or code; checked October 8, 2026.
  4. API3 Market: source verification, update parameters and plans — Official documentation or code; checked October 8, 2026.
  5. API3 data feeds: beacons, signed data, push updates and OEV — Official documentation or code; checked October 8, 2026.
  6. API3 security considerations: contracts, controls and latency — Official documentation or code; checked October 8, 2026.
  7. API3 OEV overview: auction pathways and revenue allocation — Official documentation or code; checked October 8, 2026.
  8. Legacy QRNG documentation: request–response and gas costs — Official documentation or code; checked October 8, 2026.
  9. Legacy QRNG provider reference: quantum and testnet sources — Official documentation or code; checked October 8, 2026.