PubFiDISCOVERY
Get an API key

API profile

Subscan API

Subscan API is tracked as an on-chain state and governance source for Polkadot coverage. Explorer and indexed Substrate chain API for accounts, extrinsics, governance, staking, and asset data

Coming soonNeeds re-verification
On-chain stateGovernancePolkadot
Official siteReverify source evidence

Decision guide

Use it when

Substrate account and extrinsic lookups

Check first

Generic EVM RPC workloads

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
Freemium
Agent actionability
Editorial revalidation required; runtime status separate
PubFi gateway
Not present in the active Registry
Last verified

Provider-sourced facts

Primary query
subscan api Source
Primary coverage
Substrate accounts, extrinsics, governance, staking, and asset data Source
Discovery category
On-chain state and governance Source
Auth model
API-key authentication is required for live Subscan API use Source
Commercial fact
Free API access is documented with one API key and a 5 req/sec limit; paid-plan pricing is not public in the support article Source
PubFi execution authority
Current PubFi routeability is determined only by the live signed Registry snapshot and matching runtime OpenAPI Source

Best fit and tradeoffs

Best for

  • Substrate account and extrinsic lookups
  • Polkadot and parachain governance monitoring
  • They want authenticated indexed access to Polkadot and Substrate ecosystem data without standing up a custom indexing stack first.
  • They need explorer-style reads for governance monitoring, account history, staking state, extrinsics, and assets across multiple substrate-based networks.
  • They want a faster path to workflow-ready reads than a build-your-own indexing approach usually offers.

Watchouts

  • Generic EVM RPC workloads
  • Market-wide price aggregation
  • Subscan is optimized for its published indexed API surface, so teams that need custom indexing logic or custom schema control may outgrow the default product shape.
  • You cannot directly test live API responses before registering and generating an API key, which adds real onboarding friction even for early evaluation.
  • Route usability depends on the documented effective networks for each interface, so teams cannot assume that an endpoint name automatically means the same coverage across all supported networks.

Why teams choose it

Subscan API is an indexed Substrate and Polkadot data API for teams that need account, extrinsic, governance, staking, and asset reads without operating their own indexer first. The official support site presents Subscan as an authenticated API surface for more than 70 substrate-based networks, which makes it useful when a product team wants explorer-style data access quickly.

For Discovery readers, the key distinction is that Subscan should usually be evaluated as a published indexed API product rather than as a customizable indexing framework. It is often the faster starting point for workflow-driven monitoring use cases, but teams still need to account for registration, API-key issuance, per-route network applicability, and the fact that public paid-plan pricing is not fully exposed in the support article.

What it can cover

Subscan API on-chain state coverage

Current
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Polkadot
Output contracts
Chain State Record

Subscan API governance coverage

Current
Category
Governance
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Polkadot
Output contracts
Governance Record

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
Freemium
Free tier
Free API plan allows one API key with a 5 req/sec limit.
Starting price
Contact sales
Free rate limit
5 req/sec
Paid rate limit
A higher Subscan API plan can be selected, but public paid prices and paid quotas are not published in the support article.

Data shape

Data types
Accounts, Extrinsics, Governance, Staking, Assets
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
Not listed
Source coverage status
Degraded
Editorial posture
Needs re-verification

Implementation notes

Docs

Medium

Treat account registration and API-key issuance as part of the implementation path, not as a later commercial detail, because live response validation cannot begin before those steps are complete.

Coverage

Medium

Verify the documented effective network scope for each target route before integration work starts, because endpoint usability should be checked together with per-network applicability rather than assumed globally.

Rate limits

Medium

Use the official free-plan limit as a planning constraint for prototypes and keep paid throughput assumptions out of production estimates until the target plan is confirmed.

Schema

Low

Design client integrations around the specific upstream response shape instead of assuming account, governance, staking, and asset routes all expose the same pagination and field conventions.

Auth

Medium

Keep editorial Subscan credential facts separate from PubFi execution state; only the live Registry and runtime OpenAPI can establish a current PubFi route.

Use cases

  • Track account activity across Substrate chains
  • Read governance and staking state for Polkadot ecosystem apps

Comparison snapshot

Against custom indexing platforms, Subscan is usually the better choice when governance monitoring, account history, and staking reads need to ship quickly through a ready-made indexed API surface. Teams that need deeper control over how data is indexed and queried should still evaluate whether a framework-led approach is the better fit.

PubFi friction relief

Auth

Source friction
Official Subscan support docs require account setup and API-key use before live API testing.
PubFi relief
The Discovery page separates source evaluation from PubFi execution state and reads current route status only from the live Registry.

Rate Limiting

Source friction
Official support docs list a free API rate limit while paid-plan limits are not safely projectable from public text alone.
PubFi relief
PubFi keeps public rate-limit copy status-aware instead of inventing unsupported paid throughput claims.

FAQ

What is Subscan API used for?

Subscan API is a candidate source for indexed Substrate account, transaction, governance, staking, and asset reads.

Is Subscan API available through PubFi?

Check the live PubFi Registry catalog and matching runtime OpenAPI. This editorial source profile does not claim that Subscan is currently routeable through PubFi.

When should a team compare Subscan with SubSquid?

Compare Subscan with SubSquid when the decision is between consuming a ready-made indexed API and building a more customizable indexing pipeline.