Launch Matrix

Production-readiness status for Starkscan REST, SDK, CLI, and MCP surfaces.

API reference Reference Quickstart TypeScript SDK

In this guide

Current surface states Route certification How agents should choose

Loading documentation content…

Launch matrix

Use this page when deciding which Starkscan surface an agent or client should use today.

Machine-readable source: public-client-surface-matrix.json

Current surface states

Surface	State	Current use	Main blocker
REST core API	`certified`	Production-safe for named clients on status, block, tx, token total supply, and token balance-of.	None for the certified route set.
TypeScript SDK	`beta`	Named-client beta for typed REST access.	Public npm promotion is still on the alpha channel.
Agent CLI	`beta`	Source wrapper and CLI fixtures are verified.	npm publishing access and bundled native release artifacts.
Hosted MCP HTTP	`beta`	Usable with API-key auth on the hosted `/api/mcp` endpoint.	OAuth discovery and official launcher packaging are not closed.
Official MCP launcher	`experimental`	Internal/partner preview only.	Package name, npm access, and packaged-launcher smoke.

Route certification

Route-level certification is surfaced in mezcal-openapi.yaml from the checked-in correctness manifest. The current certified launch set is intentionally narrow:

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

Indexed lists, holder analytics, privacy-pool routes, markets, and protocol routes stay beta unless the OpenAPI operation and current evidence say otherwise.

How agents should choose

Start with REST when you need the exact wire contract.
Use the TypeScript SDK when your app wants typed request construction and response shapes.
Use the CLI for shell workflows and local exports.
Use MCP only when the caller is already an MCP client.

Correctness is the hard launch gate. If a route is slow but certified, use backoff, caching, or lower concurrency. If a route is fast but still beta, do not put it in unattended production workflows without an explicit client agreement.