# Blast API | PubFi Discovery

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

Source: Discovery catalog fixtures consumed by the public Discovery routes.
Format: text/markdown; charset=utf-8
Inclusion gate: source.isIndexable is true; draft/noindex records are not emitted as markdown detail pages.
Canonical SEO rule: the HTML detail page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Agent availability rule: raw claim-safe status is preserved for provenance, but actionability uses effective agent availability. Degraded pages require revalidation even when the raw status names a gateway, x402, or MCP surface.

Canonical HTML URL: https://pubfi.ai/discovery/api/blast-api
Markdown URL: https://pubfi.ai/discovery/api/blast-api.md
Title: Blast API | PubFi Discovery
Provider: Blast API
One-liner: Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
Long description: Blast API is tracked as an RPC infrastructure source for Ethereum coverage. Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
SEO description: Blast API Discovery metadata: Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: 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 guidance:
- 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.
PubFi gateway route examples: none
Primary keyword: blast api
Keyword cluster: chain_category
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://blastapi.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, archive_access, node_latency
Protocols: rest
Auth methods: api key
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Commercial status: deprecated (Deprecated)
Free tier: Blast API products are deprecated; the official notice directs users to migrate traffic to Alchemy.
Starting price: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Pricing URL: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.; commercial docs https://blastapi.io/public-api/lumia
Free rate limit: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Paid rate limit: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Feature flags: none
Status page: https://status.blastapi.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.blastapi.io/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://blastapi.io/
- Provider docs: https://docs.blastapi.io/
- Provider status: https://status.blastapi.io/
- Blast API service deprecation notice: https://blastapi.io/public-api/lumia
Alternative APIs:
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: RPC endpoints, archive access, and Web3 infrastructure services (source https://blastapi.io/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://blastapi.io/)
Best for candidates:
- Archive and RPC endpoint access
- Web3 infrastructure provider comparisons
Not ideal for candidates:
- Market data normalization
- Governance discussion tracking
Use case candidates:
- Compare archive-capable RPC infrastructure
- Prototype blockchain reads through managed endpoints
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Blast API RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)