PubFiDISCOVERY
Get an API key

API profile

SubSquid

SubSquid is tracked as an on-chain state source for Polkadot coverage. Indexing and query infrastructure for building custom blockchain data APIs across Substrate, EVM, and other networks

Indexed onlyProvider Profile
On-chain statePolkadot
Official siteMarkdownCompare sources

Decision guide

Use it when

Custom blockchain indexing projects

Check first

Managed RPC endpoint hosting

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
API key
Pricing
Portal and Cloud pricing require product scope
Agent actionability
Not actionable
PubFi gateway
PubFi gateway not routeable yet
Last verified

Provider-sourced facts

Primary coverage
Custom blockchain indexing and query APIs across Substrate, EVM, and other networks Source
Fixture coverage
On-chain state coverage for the Polkadot fixture target Source

Best fit and tradeoffs

Best for

  • Custom blockchain indexing projects
  • Polkadot and EVM application data queries
  • They need custom blockchain indexing instead of a fixed explorer-style response model.
  • They want Substrate and EVM indexing coverage in the same technical evaluation path.
  • They expect to build application-specific query APIs where the data model is part of the product.

Watchouts

  • Managed RPC endpoint hosting
  • Off-the-shelf market price feeds
  • SubSquid is not the quickest choice when the team only needs a few ready-made account or governance reads.
  • The commercial fixture is product-scope dependent, so public pricing and rate-limit copy must stay cautious.
  • Teams should plan for indexing, schema design, and query-service operations rather than treating it as a simple RPC key.

Why teams choose it

SubSquid is strongest when a team wants to own a custom indexing and query layer rather than consume a finished explorer API. The Discovery fixture maps it to Polkadot on-chain-state coverage, while its public positioning points to indexing infrastructure across Substrate, EVM, and other networks.

For PubFi readers, SubSquid should be evaluated as a framework-style data product. It can fit teams that need schema control and application-specific datasets, but it is a heavier integration choice than a ready-made account or governance endpoint.

What it can cover

SubSquid 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

Quick start

POSTEndpoint path not listed
Style
GraphQL
Language
GraphQL
Method
POST
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

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.

Reference details

Access

Auth methods
API key
Pricing model
Portal and Cloud pricing require product scope
Free tier
Portal and Cloud pricing require product scope
Starting price
Portal and Cloud pricing require product scope
Pricing source
SQD pricing page
Free rate limit
Portal and Cloud pricing require product scope
Paid rate limit
Portal and Cloud pricing require product scope

Data shape

Data types
Indexed Chain Data, Custom Queries, Events, Transactions
Protocols
GraphQL
REST support
Not listed
GraphQL support
Yes
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
PubFi availability
Provider Profile

Implementation notes

Schema

High

Start with the target entity model before integration work, because SubSquid value comes from custom indexing and query shape rather than a universal endpoint list.

Coverage

Medium

Confirm the exact chain and dataset coverage needed for the Polkadot workflow before comparing SubSquid with SubQuery or The Graph.

Pricing

Medium

Keep commercial assumptions out of public copy unless the selected SQD product scope exposes a directly supported plan or quota.

Use cases

  • Build custom chain data APIs for application backends
  • Query indexed Substrate or EVM state for product workflows

Comparison snapshot

Compared with Subscan, SubSquid favors teams that need custom indexing control. Compared with SubQuery and The Graph, it belongs in the same framework-style shortlist where schema ownership, hosting model, and chain coverage matter more than immediate explorer reads.

PubFi friction relief

Schema Design

Source friction
The fixture and official positioning describe SubSquid as indexing and query infrastructure rather than a finished single-purpose API.
PubFi relief
PubFi Discovery frames SubSquid as a custom-indexing candidate so teams do not misread the profile as live gateway availability.

FAQ

What is SubSquid used for?

SubSquid is a candidate source for custom indexed blockchain data APIs and on-chain state reads.