At a glance
Decision summary
- Best for
- Archive and RPC endpoint access
- Watch out for
- Market data normalization
- Auth
- API key
- Pricing
- Deprecated
- Agent actionability
- Not actionable
- PubFi gateway
- PubFi gateway not routeable yet
- Last verified
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
Indexed onlyPublic source profile
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 reviewed source 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.
Capability summaries
Blast API RPC infrastructure coverage
- Category
- RPC infrastructure
- Public status
- Requested
- Auth requirement
- API key
- Procurement state
- Free Requires Auth
- Coverage
- Ethereum
- Output contracts
- Rpc Endpoint Status
Quick-start entry
POST
Endpoint path not listed- Style
- curl
- Language
- curl
- Method
- POST
- Path
- Not listed
- Requires auth
- Yes
- Provider docs
- Documentation
PubFi gateway status
PubFi gateway not routeable yet
This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
- PubFi gateway call
- Not published for this source
- Direct gateway examples
- Not available
- Next step
- Request integration or start supplier procurement review
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
Access, pricing, and protocol metadata
Access and pricing
- 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
- Pricing URL
- Blast API service deprecation notice
- Free rate limit
- Deprecated
- Paid rate limit
- Deprecated
Protocols and outputs
- 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
Provider and review status
- Documentation
- Provider docs
- Doc quality score
- Not listed
- Status page
- Provider status
- Public fixture status
- Current
- Raw claim-safe status
- Public source profile
- Page tier
- Tier 2
Implementation notes
Gotcha
Treat the deprecated status as a primary implementation blocker for new Blast API adoption.
Coverage
Use the page for historical comparison or migration context rather than active endpoint selection.
Pricing
Do not publish plan or rate-limit projections for deprecated Blast API products.
Use case candidates
- 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 reduction
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.
Official source links
Agent-readable resources
Alternatives and hubs
FAQ
What is Blast API used for?
Blast API is a candidate source for RPC endpoints, archive access, and Web3 infrastructure workflows.