API profile

Blockchair API

Blockchair API is an automation-built evidence profile for Blockchair public API resources. Discovery has historical docs evidence, but the official docs and homepage freshness locators are currently unreachable to machine fetches and PubFi does not certify gateway runtime support for this provider

RequestedProvider Profile

Decision guide

Use it when

Evaluating Blockchair public API docs

Check first

Assuming PubFi gateway availability without adapter certification

PubFi status

Provider Profile

The page is an AI/Codex-processed public Provider Profile and does not claim PubFi integration, gateway access, x402 payment, or MCP tooling.

Key facts

Auth
Not listed
Pricing
Public commercial facts require product-specific review
Agent actionability
Not actionable
PubFi gateway
PubFi gateway not routeable yet
Last verified

Provider-sourced facts

Public docs evidence
Blockchair has public API or documentation evidence available from public sources. Source
PubFi gateway status
Automation-built Provider Profile; PubFi gateway support is not certified.

Best fit and tradeoffs

Best for

  • Evaluating Blockchair public API docs
  • They want an internal starting point for evaluating Blockchair API documentation.
  • They need to compare Blockchair against nearby crypto data providers before runtime integration work.
  • They want claim-safe evidence that can be promoted later when source freshness and adapter certification are both clear.

Watchouts

  • Assuming PubFi gateway availability without adapter certification
  • Automation-built profiles may have incomplete category, pricing, quota, or endpoint coverage until deeper docs parsing runs.
  • Public docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, and terms before treating the provider as production-callable.

Why teams choose it

Blockchair API is an automation-built evidence profile based on public API corpus evidence. It helps teams inspect Blockchair docs, product naming, and on chain state fit before any runtime adapter or commercial approval work begins.

Discovery keeps this profile behind noindex and out of LLM export because the official docs and homepage freshness locators are currently unreachable to machine fetches. Inclusion means public evidence was processed for follow-up review, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, or supplier procurement for Blockchair.

What it can cover

Blockchair API on chain state evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Bitcoin, Ethereum
Output contracts
Chain State Record

PubFi gateway

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 production-callable.
  • 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.

Implementation notes

Docs

Medium

Review Blockchair public docs, authentication requirements, and the unreachable docs and homepage freshness locators before any adapter certification work starts.

Coverage

Medium

Treat the current Blockchair API profile as processed evidence, not as complete coverage of every chain, endpoint, or product surface.

Schema

Low

Use endpoint-specific docs evidence before deriving runtime request or response contracts.

Use cases

  • Compare Blockchair API evidence before runtime integration work

Comparison snapshot

Blockchair API should be compared with providers that cover similar on chain state workflows. The current automation output is enough for internal follow-up triage, but not for public Discovery visibility, LLM export, or certified gateway routing.

PubFi friction relief

Docs

Source friction
Blockchair public docs are available as public documentation evidence.
PubFi relief
PubFi Discovery retains the public evidence as a noindex evidence profile and separates it from gateway certification.

FAQ

Is Blockchair API available through the PubFi gateway?

This Provider Profile is automation-built from public evidence and does not certify PubFi gateway availability.

Noindex status

  • publication metadata is not signed off
  • publication sign-off timestamp is missing
  • publication metadata is marked noindex
  • publication metadata is not public-page ready
  • source editorial fixture review is not signed off