Explorer Documentation

Public API access

How integrators use read-only explorer APIs today, how managed RPC keys work on /access, and the planned path if public rate limits require API keys.

Account access Wallet tools Operations hub

Decision summary (2026-05-23)

Blockscout read API (/api/v2/*) and the public JSON surfaces listed below remain unauthenticated for integrators on the public explorer domain.
Managed RPC product keys are issued through wallet-authenticated Account access (Core RPC / thirdweb-rpc products). These keys gate managed RPC endpoints — not the public Blockscout read layer.
If abuse or rate limits require change, the preferred near-term path is Option B: nginx/API-gateway throttling with optional X-API-Key for higher quotas. A full external developer portal remains optional.

Read-only public endpoints (no key)

Blockscout stats
Chain head, gas, and indexer summary.
Bridge status JSON
Mission-control relay posture snapshot.
Route matrix
Token-aggregation live and planned routes.
Wallet networks
Published chain metadata for wallet onboarding.
WalletConnect config
Published WalletConnect v2 posture and browser-auth fallback.
Blockscout v2
Same-origin /api/v2/stats, blocks, transactions, tokens, and address endpoints proxied to Blockscout.

Requesting higher limits or RPC keys

For managed RPC access, connect a wallet on Wallet tools then open Account access to create scoped keys with tier, product, expiry, and optional monthly quota.

For integrator questions about public JSON endpoints or future Blockscout key policy, email support@d-bis.org.