Blast
Blast is an Ethereum Layer 2 network (OP Stack-derived, post-Pacific Meridian upgrade) that pays native yield on bridged ETH and stablecoins via auto- rebasing tokens — roughly 4% on ETH (from Ethereum staking) and 5% on USDB (from T-Bill protocols) — and programmatically returns a share of net gas revenue to dApps. Mainnet runs at chain ID 81457 with public JSON-RPC at rpc.blast.io and a Sepolia testnet at chain ID 168587773 / sepolia.blast.io. Developer surfaces include Blastscan and Sepolia Blastscan explorers, the native bridge, USDB stablecoin, and the gas / yield smart contracts.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Blast the way a machine reads it — 16 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Blast scores 42.6/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Blast
Each block below is one kind of artifact we hold for Blast. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Blast Mainnet JSON-RPC
Public Ethereum-compatible JSON-RPC endpoint for Blast mainnet (chain ID 81457). Supports the standard eth_* method set used by web3 clients, wallets, and indexers.
Blast Sepolia Testnet JSON-RPC
Public JSON-RPC endpoint for the Blast Sepolia testnet (chain ID 168587773), used for application development, integration testing, and bridge testing before deploying to mainnet.
Blast Native Yield Contracts
Auto-rebasing yield mechanism for ETH and USDB on Blast. Contracts expose configuration calls to opt accounts into automatic, claimable, or void yield modes, used by every dApp ...
Blast Gas Revenue API
Programmatic interface for dApps to claim back a share of the net gas revenue generated by their contracts on Blast, configured per-contract via the Blast precompile.
USDB Native Stablecoin
USDB is Blast's native auto-rebasing stablecoin, redeemable 1:1 for DAI when bridged back to Ethereum. Backed by T-Bill protocols and integrated directly into the Blast bridge.
Blast Bridge
Canonical Ethereum-Blast bridge for ETH, USDB, and supported ERC-20 tokens. UI lives at bridge.blast.io and is backed by the OP Stack standard bridge contracts.
Blastscan Block Explorer
Etherscan-style block explorer for Blast mainnet — transactions, blocks, addresses, contracts, tokens, and Solidity source verification.
Blastscan Sepolia Testnet Explorer
Blastscan instance for the Blast Sepolia testnet, supporting transaction lookup and contract verification for testnet deployments.
Blast JSON-RPC API
Ethereum-compatible JSON-RPC methods exposed by the Blast node.
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Blast Network JSON-RPC
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Blast Network Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Blast Network Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Blast — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/blast-network · machine-readable index on apis.io