Route Certification

Starkscan publishes a clear certification state for each documented route.

Every public OpenAPI operation carries x-starkscan-certification:

The public OpenAPI contract and /route-certification-evidence.json publish the route state, supported access tier, and audience so applications can choose an appropriate integration surface.

Certified launch set

The current certified launch set is intentionally narrow:

• GET /v1/{chain}/status
• GET /v1/{chain}/block/{number_or_hash}
• GET /v1/{chain}/block-at-timestamp
• GET /v1/{chain}/tx/{tx_hash}
• GET /v1/{chain}/token/{token}/total-supply
• GET /v1/{chain}/token/{token}/balance-of/{address}

For deterministic token reads, pass a concrete block_tag by block number or block hash. latest and pending are live state, not replayable accounting evidence.

Workflow evidence

Endpoint contracts are not enough for agents. Starkscan also defines workflow contracts for multi-step tasks.

The first workflow is the accounting balance path:

timestamp -> block-at-timestamp closest=before -> token balance-of at block

Use it when an accounting team needs one token balance for one account at one point in time. It does not infer historical portfolios or resolve ticker symbols to token contracts.