At a glance
Decision summary
- Best for
- Custom blockchain data indexing
- Watch out for
- Raw RPC endpoint hosting
- Auth
- API key
- Pricing
- Marketplace pricing
- Agent actionability
- Not actionable
- PubFi gateway
- PubFi gateway not routeable yet
- Last verified
SubQuery Network
SubQuery Network is tracked as an on-chain state source for Polkadot coverage. Decentralized indexing and query services for blockchain application data across Polkadot, Ethereum, and other ecosystems
Indexed onlyPublic source profile
Best fit and tradeoffs
Best for
- Custom blockchain data indexing
- Polkadot and Ethereum application query layers
- They need a managed or networked indexing path for blockchain application data.
- They want a Polkadot-relevant alternative to SubSquid and The Graph.
- They expect to maintain a project-specific data model instead of relying only on provider-defined endpoints.
Watchouts
- Raw RPC endpoint hosting
- Market-wide price aggregation
- SubQuery requires project and query design work before the source becomes useful to an application.
- The fixture keeps commercial facts product-scope dependent, so pricing and plan language should not be flattened into a single public price.
- Teams comparing it with Subscan should account for build effort, not only feature coverage.
Why teams choose it
SubQuery Network is an indexing and query platform for teams that need blockchain application data with project-specific data models. The Discovery fixture maps it to Polkadot on-chain-state coverage and lists SubSquid, Subscan, and The Graph as the most relevant alternatives.
The practical distinction is control. SubQuery is a better fit when a team expects to define an indexer project and query surface; it is less direct than a productized explorer API for simple account, extrinsic, or governance lookups.
Capability summaries
SubQuery Network on-chain state coverage
- Category
- On-chain state
- Public status
- Requested
- Auth requirement
- API key
- Procurement state
- Free Requires Auth
- Coverage
- Polkadot
- Output contracts
- Chain State Record
Quick-start entry
POST
Endpoint path not listed- Style
- GraphQL
- Language
- GraphQL
- Method
- POST
- Path
- Not listed
- Requires auth
- Yes
- Provider docs
- Documentation
PubFi gateway status
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 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.
Access, pricing, and protocol metadata
Access and pricing
- Auth methods
- API key
- Pricing model
- Marketplace pricing
- Free tier
- SubQuery access uses project and node-operator scoped Flex plans; no provider-wide free tier is safe to flatten.
- Starting price
- Marketplace pricing
- Free rate limit
- Marketplace pricing
- Paid rate limit
- Marketplace pricing
Protocols and outputs
- 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
Provider and review status
- Documentation
- Provider docs
- Doc quality score
- Not listed
- Status page
- Not listed
- Public fixture status
- Current
- Raw claim-safe status
- Public source profile
- Page tier
- Tier 1
Implementation notes
Schema
Define the indexed entities and query expectations before choosing SubQuery, because the integration depends on project-level indexing design.
Coverage
Verify whether the target Polkadot or EVM workflow is supported by the chosen SubQuery project and deployment model.
Pricing
Use product-scope commercial labels until the exact SubQuery access path exposes supported public plan facts.
Use case candidates
- Expose indexed application data through query APIs
- Evaluate decentralized indexer coverage for product backends
Comparison snapshot
SubQuery sits between ready-made indexed APIs and decentralized indexing protocols. It is closer to SubSquid and The Graph than to Subscan, and the right choice depends on project-level indexing requirements rather than generic chain support.
PubFi friction reduction
Project Setup
- Source friction
- The official product and fixture describe decentralized indexing and query services rather than a fixed response API.
- PubFi relief
- Discovery keeps SubQuery as a reviewed source profile with integration-request language instead of implying a turnkey PubFi route.
Official source links
Agent-readable resources
Alternatives and hubs
FAQ
What is SubQuery Network used for?
SubQuery Network is a candidate source for indexed blockchain application data and custom query workflows.