PubFiDISCOVERY
Get an API key

API profile

Blast API

Blast API is tracked as an RPC infrastructure source for Ethereum coverage. Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services

Coming soonNeeds re-verification
RPC infrastructureEthereum
Official siteReverify source evidence

Decision guide

Use it when

Archive and RPC endpoint access

Check first

Market data normalization

PubFi status

Needs re-verification

The editorial profile remains useful, but its public evidence is degraded. Reverify upstream docs and commercial terms; use the live Registry and runtime OpenAPI for PubFi execution decisions.

Key facts

Auth
API key
Pricing
Deprecated
Agent actionability
Editorial revalidation required; runtime status separate
PubFi gateway
Not present in the active Registry
Last verified

Provider-sourced facts

Primary coverage
RPC endpoints, archive access, and Web3 infrastructure services Source
Fixture coverage
RPC infrastructure coverage for the Ethereum fixture target Source

Best fit and tradeoffs

Best for

  • Archive and RPC endpoint access
  • Web3 infrastructure provider comparisons
  • They need to identify Blast API in an existing provider shortlist or migration conversation.
  • They are reviewing historical RPC provider alternatives and need current status context.
  • They want to compare deprecated infrastructure records without losing the route-level evidence trail.

Watchouts

  • Market data normalization
  • Governance discussion tracking
  • The deprecated commercial status blocks positive plan or onboarding claims.
  • Teams starting a new RPC integration should compare active alternatives such as QuickNode, Alchemy, or Infura first.
  • Any migration or replacement guidance should stay tied to official evidence and not overstate PubFi routing support.

Why teams choose it

Blast API is tracked as an Ethereum RPC infrastructure source, but the current commercial fixture marks Blast API products as deprecated and points users toward migration context. That status is the most important fact for readers.

Discovery should keep the page indexable only as a Provider Profile with clear caution language. It can help teams understand why Blast appears in historical or alternative lists, but it should not be positioned as a fresh greenfield recommendation.

What it can cover

Blast API RPC infrastructure coverage

Current
Category
RPC infrastructure
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Ethereum
Output contracts
Rpc Endpoint Status

Quick start

POSTEndpoint path not listed
Style
curl
Language
curl
Method
POST
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

PubFi gateway

Not present in the active Registry

The active signed Registry generation has no route for this provider. Discovery inclusion and upstream documentation do not make a provider executable through PubFi.

Runtime status
not_present
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Use the official provider documentation for direct integration.
  • A future collected source becomes executable only after the normal evidence, policy, health, and generation pipeline accepts it.

Reference details

Access

Auth methods
API key
Pricing model
Deprecated
Free tier
Blast API products are deprecated; the official notice directs users to migrate traffic to Alchemy.
Starting price
Deprecated
Free rate limit
Deprecated
Paid rate limit
Deprecated

Data shape

Data types
Rpc Endpoints, Archive Access, Node Latency
Protocols
REST
REST support
Yes
GraphQL support
Not listed
WebSocket support
Not listed
Streaming support
Not listed
Webhook support
Not listed
Feature flags
Not listed
SDKs
Not listed

Public evidence

Documentation
Provider docs
Status page
Provider status
Source coverage status
Degraded
Editorial posture
Needs re-verification

Implementation notes

Gotcha

High

Treat the deprecated status as a primary implementation blocker for new Blast API adoption.

Coverage

Medium

Use the page for historical comparison or migration context rather than active endpoint selection.

Pricing

Medium

Do not publish plan or rate-limit projections for deprecated Blast API products.

Use cases

  • Compare archive-capable RPC infrastructure
  • Prototype blockchain reads through managed endpoints

Comparison snapshot

Blast API belongs in comparisons mainly as a deprecated or migration-context source. QuickNode, Alchemy, and Infura are more appropriate active RPC alternatives under the current fixture state.

PubFi friction relief

Deprecated Source

Source friction
The commercial metadata status for Blast API is deprecated in the fixture.
PubFi relief
Discovery keeps deprecated status visible so agents and users do not infer active availability from page existence.

FAQ

What is Blast API used for?

Blast API is a candidate source for RPC endpoints, archive access, and Web3 infrastructure workflows.