DeFi Data API / planned API

DeFi context.
Evidence first.

A transfer is a technical movement. A swap, deposit or loan is an interpretation. Our planned DeFi data API keeps the connection between the two explicit.

Read the technical preview Early-access plans

In development · no public production endpoint

CONTRACT DIRECTIONILLUSTRATIVE

{
  "economicStatus": "unknown",
  "economicActions": [],
  "evidence": [
    "transaction",
    "receipt",
    "logs"
  ],
  "reviewRequired": true
}

This example explains a design principle. It is not a live API response or a stable production schema.

02 / Why this matters

Recognition is only the first step.

Knowing a protocol name does not prove what happened economically. A reliable decoder needs the right deployment, contract version and historical block context. Our approach starts with raw evidence and only adds an interpretation when that interpretation can be tested.

Source evidence and interpretation should travel together. A downstream product must be able to distinguish observed data, a supported interpretation and an unresolved question.

The intended contract

Decoder families

The roadmap groups reusable patterns such as AMMs, lending and vaults. Protocol-specific configuration must account for deployments, versions and upgrades.

Provenance for interpretation

Planned economic actions will reference the technical events they explain. Decoder versions and their supported scope must be inspectable.

Unknown is a valid outcome

An unrecognised event should remain available as raw evidence. Unsupported interpretations must stay unknown or require review, rather than silently disappearing.

USE CASES / Built for technical teams

A better basis for your product.

Accounting integrations

Keep proposed economic interpretations separate from existing customer records.

Protocol research

Compare contract behaviour without relying solely on provider labels.

Wallet experiences

Explain supported actions while showing the limits of the decoder.

API in development

What is available today?

The DeFi API is an architecture and decoder roadmap, not a live protocol-coverage catalogue. Registry entries are not certified decoders. No production DeFi breadth, historical completeness or protocol-count commitment is being offered.

Read the implementation status

QUESTIONS / DeFi Data API

Before you build.

Which DeFi protocols are supported?

There is no public production support list yet. Each future decoder family will need deployment-specific tests and a declared coverage boundary.

Are USD values used as token amounts?

No. A monetary valuation is not a token quantity. The technical contract uses exact atomic amounts and leaves uncertain metadata unresolved.

Can the same event create two economic actions?

Preventing duplicate economic attribution is a design requirement. Future integrations must establish a tested mapping between raw movements and interpretations before producing bookings.

Built with a long view

Help shape the next
layer of blockchain data.

Explore the direction. Early access is not open yet.

Early-access plans

DeFi context.Evidence first.