Blockchain Data API / planned API

Start with the chain.
Keep the evidence.

Blockchain intelligence needs a dependable raw layer. Indexbase is being built to preserve original data, track where it came from and make its limits queryable.

Read the technical preview Early-access plans

In development · no public production endpoint

CONTRACT DIRECTIONILLUSTRATIVE

{
  "dataKinds": [
    "blocks",
    "transactions",
    "receipts",
    "logs",
    "traces"
  ],
  "historyComplete": false,
  "source": "synthetic-test-dataset"
}

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

03 / Why this matters

Data infrastructure should be inspectable.

A normalised record is useful, but it should not replace its source. The local M1 implementation preserves original RPC response bytes with a digest, source reference and retrieval time. This supports reproducible checks rather than a black-box feed.

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

Raw provenance

Retain the original response alongside technical records. Distinguish the digest of archived bytes from an Ethereum block or transaction hash.

Chain and fork context

The Ethereum prototype validates chain and genesis identity, block relationships and receipt completeness. Reorganisations and finality conflicts are explicit states.

Coverage by data kind

Blocks, transactions, receipts, logs and traces have separate coverage. A source that supplies receipts may still lack the historical state needed for traces.

USE CASES / Built for technical teams

A better basis for your product.

Data platforms

Build a source layer that can be replayed and checked independently.

Analytics teams

Separate missing evidence from a genuine absence of activity.

API products

Make coverage and provenance part of the downstream data contract.

API in development

What is available today?

Ethereum is the first implementation focus. BSC, Solana and Bitcoin are planned modules, not live integrations. The production pipeline is intended to use self-operated nodes; a real-node pilot has not yet been completed.

Read the implementation status

QUESTIONS / Blockchain Data API

Before you build.

Is this already a live multi-chain service?

No. The tested implementation is a local Ethereum raw indexer using synthetic fixtures. Additional chains are planned.

Will the data pipeline require commercial provider labels?

The target architecture uses self-operated nodes and evidence-backed decoders. The local prototype does not require a commercial blockchain data API.

Does coverage include every internal movement?

Only when suitable traces are available and pass the supported checks. Missing trace data must be stated explicitly.

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

Start with the chain.Keep the evidence.