Launch Matrix
Production-readiness status for Starkscan REST, RPC, SDK, CLI, and MCP surfaces.
Loading documentation content…
Production-readiness status for Starkscan REST, RPC, SDK, CLI, and MCP surfaces.
Use this page when deciding which Starkscan surface an agent or client should use today.
Machine-readable source: public-client-surface-matrix.json
Package trust surface: Package trust
| Surface | Public label | 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. |
| Starkscan RPC provider | beta | JSON-RPC provider pilot for named clients that need starknet.js-style reads, simulation, fees, storage, receipts, events, and batch calls. Header auth is preferred; /rpc/v0_10/{chain}/{token} exists for clients that only accept nodeUrl. | Method-level observability, method-level conformance breadth, writes, WebSockets, and short-lived RPC-only URL tokens before full-provider promotion. |
| TypeScript SDK | alpha | 0.1.0-alpha.1 is published on the alpha tag, imports under Node ESM, and passed live status smoke with STARKSCAN_BASE_URL=https://starkscan.co/api. | Resolve publish-control / public-source metadata before promotion beyond alpha. |
| Agent CLI | alpha | 0.1.0-alpha.1 is published on the alpha tag with bundled native artifacts, manifest/checksum verification, and live status / doctor smoke with STARKSCAN_BASE_URL=https://starkscan.co/api. | Resolve publish-control / public-source metadata before promotion beyond alpha. |
| Hosted MCP HTTP | beta | Usable with API-key auth on the hosted /api/mcp endpoint; protected-resource discovery is live. | None for the hosted HTTP transport; package launcher promotion is tracked separately. |
| Official MCP launcher | alpha | 0.1.0-alpha.1 is published on the alpha tag, delegates to the exact matching CLI version, and passed live doctor smoke with STARKSCAN_BASE_URL=https://starkscan.co/api. | Resolve publish-control / public-source metadata before promotion beyond alpha. |
The machine-readable matrix still uses experimental for package surfaces whose
publish-control or public-source decisions are incomplete. The human-facing
package label is alpha, matching the npm channel and homepage.
Route-level certification is surfaced in
starkscan-openapi.yaml from the checked-in correctness
manifest. The current certified launch set is intentionally narrow:
GET /v1/{chain}/statusGET /v1/{chain}/block/{number_or_hash}GET /v1/{chain}/tx/{tx_hash}GET /v1/{chain}/token/{token}/total-supplyGET /v1/{chain}/token/{token}/balance-of/{address}GET /v1/{chain}/block-at-timestamp is a beta accounting helper for turning a
calendar-close instant into the concrete block number used by the certified
balance-of route. It stays beta until its timestamp resolver gate is part of
the recurring launch benchmark.
The Starkscan RPC provider at POST /api/v1/{chain}/rpc is separate from the
certified REST launch set. It is beta: useful for named clients, but not yet a
full-provider claim for writes, WebSockets, traces, successful signed
simulation/fee fixtures, or broad method-level SLOs. Server clients should use
X-Starkscan-Api-Key; SDKs/tools that cannot attach headers can use
/rpc/v0_10/{chain}/{token} as a compatibility nodeUrl. Treat that full URL
as a secret.
Indexed lists, holder analytics, privacy-pool routes, markets, and protocol
routes stay beta unless the OpenAPI operation and current evidence say
otherwise.
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.
Package trust is a separate gate. A package can wrap certified routes while
still being experimental if its tokenless publish path, public-source
metadata, or external risk signals are incomplete. npm provenance is not
available while the canonical source repository is private. See
Package trust.
For certified token reads, latest and pending remain live moving-state
shortcuts. Agents that need reproducible correctness should pass an explicit
block number or block hash as block_tag; the launch gate compares the route
and Starknet RPC at that same exact block.