Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryData and agents2020Design paperCorpus record

API3: first-party oracles and Airnode

API3. API3.

API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
2

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    First-party is a claim about who signs. If a middleman still signs, the deployment is not this sentence.

  2. Claim 02 · Paper model

    The proposal

    API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.

  3. Claim 03 · Paper model

    The mechanism

    Airnode is the gateway software the docs specify. It is not a consensus protocol.

  4. Claim 04 · Paper model

    The bound

    No provider count is stated here.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    First-party is a claim about who signs. If a middleman still signs, the deployment is not this sentence.

    Model

    What has to hold

    You are reading API3's docs. A provider's marketing page is not the gateway specification.

    Falsifier

    What would retire it

    Who holds the signing key for the feed: the API operator, or a delegate?

  2. 02 The proposal

    Observation

    What the study says

    API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.

    Model

    What has to hold

    You are reading API3's docs. A provider's marketing page is not the gateway specification.

    Falsifier

    What would retire it

    What does the contract do if the provider stops updating?

  3. 03 The mechanism

    Observation

    What the study says

    Airnode is the gateway software the docs specify. It is not a consensus protocol.

    Model

    What has to hold

    You are reading API3's docs. A provider's marketing page is not the gateway specification.

    Falsifier

    What would retire it

    Is there an aggregation set, and who chooses it?

  4. 04 The bound

    Observation

    What the study says

    No provider count is stated here.

    Model

    What has to hold

    You are reading API3's docs. A provider's marketing page is not the gateway specification.

    Falsifier

    What would retire it

    What does the contract do if the provider stops updating?

03 Sequence

One action, as an operating tape

  1. 01Airnode is the gateway software the docs specify. It is not a consensus protocol.
  2. 02A provider's honesty is the assumption. More providers are more assumptions, not automatically less.
  3. 03On-chain aggregation, if used, is a second contract with its own parameters.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A first-party signature can still be wrong, stale, or paused by the provider.

  2. What actually moves

    The cut

    A provider's honesty is the assumption. More providers are more assumptions, not automatically less.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    No provider count is stated here.

  3. What a later deployment may change

    The cut

    On-chain aggregation, if used, is a second contract with its own parameters.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading API3's docs. A provider's marketing page is not the gateway specification.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

This is not a statement that any particular API is decentralised.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

First-party is a claim about who signs. If a middleman still signs, the deployment is not this sentence.

What the design proposes

  • Airnode is the gateway software the docs specify. It is not a consensus protocol.
  • A provider's honesty is the assumption. More providers are more assumptions, not automatically less.
  • On-chain aggregation, if used, is a second contract with its own parameters.

How the mechanism is specified

  • Airnode is the gateway software the docs specify. It is not a consensus protocol.
  • A provider's honesty is the assumption. More providers are more assumptions, not automatically less.
  • On-chain aggregation, if used, is a second contract with its own parameters.

What this page does not treat as proven

  • No provider count is stated here.
  • A first-party signature can still be wrong, stale, or paused by the provider.
  • This is not a statement that any particular API is decentralised.

Why the desk still reads it

API3's design asks the API provider to run the oracle, so the signer is the party who already operates the API, rather than a third-party node repeating it.

09 Lexicon

Terms, opened into the record

First-party oracle
The API operator signs the data the contract reads.
Airnode
The gateway described in the API3 docs. It is software, not a guarantee of uptime.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.