Subscan API

Name: PubFi
Brand: PubFi

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

Profile readyProvider Profile

Official site Markdown Compare sources

Decision guide

Use it when

Substrate account and extrinsic lookups

Check first

Generic EVM RPC workloads

Profile 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: API key
Pricing: Freemium
Agent actionability: Editorial only; runtime status separate
PubFi gateway: Checking Registry…
Last verified: Aug 26, 2026

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

Documented

Category: On-chain state
Catalog visibility: Indexed Only
Auth requirement: API key
Integration disposition: Eligible Free Credentials
Coverage: Polkadot
Output contracts: Chain State Record

Subscan API governance coverage

Documented

Category: Governance
Catalog visibility: Indexed Only
Auth requirement: API key
Integration disposition: Eligible Free Credentials
Coverage: Polkadot
Output contracts: Governance Record

Quick start

GEThttps://acala.api.subscan.io/api/now

Style: REST
Language: HTTP
Method: GET
Path: https://acala.api.subscan.io/api/now
Requires auth: Yes
Provider docs: Documentation

PubFi gateway

Checking live Registry…

Editorial evidence is available while current route availability loads.

Runtime status: Loading
Active capabilities: —
PubFi auth headers: Authorization: Bearer <PubFi API key>
Typed contract: Runtime OpenAPI

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
Pricing source: Subscan API plan and rate-limit support article
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: Current
Editorial posture: Provider Profile

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

Aug 26, 2026

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

Aug 26, 2026

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.

Official links

Official site Provider docs Subscan API plan and rate-limit support article PubFi execution authority

Agent resources

Agents guide LLMs full export Subscan API Markdown detail

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.

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

Profile readyProvider Profile

On-chain state Governance Polkadot

Official site Markdown Compare sources

Decision guide

Use it when

Substrate account and extrinsic lookups

Check first

Generic EVM RPC workloads

Profile 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: API key
Pricing: Freemium
Agent actionability: Editorial only; runtime status separate
PubFi gateway: Available in the active RegistryChecking Registry…
Last verified: Aug 26, 2026

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

What it can cover

Subscan API on-chain state coverage

Documented

Category: On-chain state
Catalog visibility: Indexed Only
Auth requirement: API key
Integration disposition: Eligible Free Credentials
Coverage: Polkadot
Output contracts: Chain State Record

Subscan API governance coverage

Documented

Category: Governance
Catalog visibility: Indexed Only
Auth requirement: API key
Integration disposition: Eligible Free Credentials
Coverage: Polkadot
Output contracts: Governance Record

Quick start

GEThttps://acala.api.subscan.io/api/now

Style: REST
Language: HTTP
Method: GET
Path: https://acala.api.subscan.io/api/now
Requires auth: Yes
Provider docs: Documentation

PubFi gateway

Available in the active Registry

The currently installed signed Registry generation contains an executable route for this provider. The same generation drives request matching, runtime OpenAPI, and this public view.

Runtime status: ready
Active capabilities: 552
PubFi auth headers: Authorization: Bearer <PubFi API key>
Typed contract: Runtime OpenAPI

GET /v1/gateway/subscan/api/now
route-registered-c5a0827e62e1dffc1233b0731d37b1040a0a30736fbc16f07d042d91087557eaStatus: ready
GET /v1/gateway/subscan/{network}/api/now
route-registered-d52e3a3afb77555cb19e72d3d8687e24b90b3d142a5666d68d8228de8ddea4a9Status: ready
GET /v1/gateway/subscan/api/scan/collator/meta
route-registered-536cead4c7d41f142c507d96689d909b40d878bf1a2c7ae458fe1d4c7d246d50Status: ready
GET /v1/gateway/subscan/{network}/api/scan/collator/meta
route-registered-f86c3ab7edc9114b576209ca8d8e47d3a9501c0b0468c7fb0244777566bb68c7Status: ready
GET /v1/gateway/subscan/api/scan/contracts/verify/compiler_images
route-registered-2faa7aaea612b6bddde41c59cfede8f4804b7f43b0e4d2f7c0a0dc4d9aa245bdStatus: ready
GET /v1/gateway/subscan/{network}/api/scan/contracts/verify/compiler_images
route-registered-b07a8b66729184aae7659fc2c60857c206ba1f66dc8b04b071782fd0195d50c1Status: ready
GET /v1/gateway/subscan/api/scan/contracts/verify/compiler_version
route-registered-90c9a887f6ffd82b187512dae69d9ee345c46ffe260822d81ff79d05675724ddStatus: ready
GET /v1/gateway/subscan/{network}/api/scan/contracts/verify/compiler_version
route-registered-d5fb173e79d19f53e1d7fbeb27fe03f8d68fb2f2f42a78a8f69ce232e2315b2dStatus: ready

544 additional route variants are available from the exact capability API and Runtime OpenAPI.

Accepted PubFi auth headers: Authorization: Bearer <PubFi API key>.
Upstream credentials remain server-side; callers send only a PubFi API key.
Use the runtime OpenAPI for the exact typed query, body, and response contract.

Checking live Registry…

Editorial evidence is available while current route availability loads.

Runtime status: Loading
Active capabilities: —
PubFi auth headers: Authorization: Bearer <PubFi API key>
Typed contract: Runtime OpenAPI

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
Pricing source: Subscan API plan and rate-limit support article
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: Current
Editorial posture: Provider Profile

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

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

PubFi friction relief

Auth

Aug 26, 2026

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

Aug 26, 2026

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.

Official links

Official site Provider docs Subscan API plan and rate-limit support article PubFi execution authority

Agent resources

Agents guide LLMs full export Subscan API Markdown detail

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.

SASubscan API

Decision guide

Use it when

Check first

Profile status

Key facts

Provider-sourced facts

Best fit and tradeoffs

Best for

Watchouts

Why teams choose it

What it can cover

Subscan API on-chain state coverage

Subscan API governance coverage

Quick start

PubFi gateway

Reference details

Access

Data shape

Public evidence

Implementation notes

Docs

Coverage

Rate limits

Schema

Auth

Use cases

Comparison snapshot

PubFi friction relief

Auth

Rate Limiting

Official links

Agent resources

Alternatives and hubs

Alternative APIs

Comparison pages

Category hubs

Chain hubs

FAQ

What is Subscan API used for?

Is Subscan API available through PubFi?

When should a team compare Subscan with SubSquid?

SASubscan API

Decision guide

Use it when

Check first

Profile status

Key facts

Provider-sourced facts

Best fit and tradeoffs

Best for

Watchouts

Why teams choose it

What it can cover

Subscan API on-chain state coverage

Subscan API governance coverage

Quick start

PubFi gateway

Reference details

Access

Data shape

Public evidence

Implementation notes

Docs

Coverage

Rate limits

Schema

Auth

Use cases

Comparison snapshot

PubFi friction relief

Auth

Rate Limiting

Official links

Agent resources

Alternatives and hubs

Alternative APIs

Comparison pages

Category hubs

Chain hubs

Subscan API

Subscan API