At a glance
Decision summary
- Best for
- Polkadot RPC and archive access
- Watch out for
- Standalone market price datasets
- Auth
- API key
- Pricing
- Freemium
- Agent actionability
- Requires revalidation
- PubFi gateway
- PubFi gateway not routeable yet
- Last verified
OnFinality
OnFinality is tracked as an RPC infrastructure and on-chain state source for Polkadot coverage. Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks
Coming soonPublic source profile
Best fit and tradeoffs
Best for
- Polkadot RPC and archive access
- Teams comparing managed blockchain infrastructure providers
- They need Polkadot RPC or archive infrastructure from a provider with explicit Polkadot positioning.
- They want managed infrastructure instead of operating their own nodes.
- They need a Polkadot-first comparison point against QuickNode, Ankr, or other broad RPC providers.
Watchouts
- Standalone market price datasets
- Automation-approved governance summaries
- OnFinality is infrastructure-led, so it does not replace an indexed API such as Subscan for explorer-style records.
- Response-unit limits and plan tiers matter for production workloads and should be checked against the official support material.
- Broad multichain providers may be stronger if the team needs one vendor across many non-Polkadot networks.
Why teams choose it
OnFinality is a Polkadot-oriented managed infrastructure provider for RPC, archive nodes, and adjacent on-chain-state access. Discovery tracks it as both RPC infrastructure and on-chain-state coverage for the Polkadot fixture target.
It is a good starting point when the source decision is about managed node infrastructure rather than an indexed analytics API. Teams should evaluate endpoint type, archive needs, response-unit limits, and Polkadot network scope before comparing it with broader multichain RPC providers.
Capability summaries
OnFinality RPC infrastructure coverage
- Category
- RPC infrastructure
- Public status
- Requested
- Auth requirement
- API key
- Procurement state
- Free Requires Auth
- Coverage
- Polkadot
- Output contracts
- Rpc Endpoint Status
OnFinality 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
- curl
- Language
- curl
- 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
- Freemium
- Free tier
- Developer plan includes 400,000 RPC response units/day and up to 40 response units/sec.
- Starting price
- $49 / month
- Pricing URL
- Official pricing
- Free rate limit
- Up to 40 RPC response units/sec
- Paid rate limit
- Growth 200, Accelerate 500, Ultimate custom RPC response units/sec
Protocols and outputs
- Data types
- Rpc Endpoints, Archive Nodes, Chain State, Node Latency
- 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
Provider and review status
- Documentation
- Provider docs
- Doc quality score
- Not listed
- Status page
- Provider status
- Public fixture status
- Degraded
- Raw claim-safe status
- Public source profile
- Page tier
- Tier 2
Implementation notes
Coverage
Confirm the target Polkadot network, archive requirement, and method set before treating OnFinality as interchangeable with generic Ethereum RPC providers.
Rate limits
Use response-unit limits rather than raw request counts when planning workload size from the public commercial fixture.
Auth
Plan for API-key or endpoint credential handling separately from PubFi source discovery because this profile does not claim universal gateway access.
Use case candidates
- Route application reads to managed Polkadot infrastructure
- Compare RPC infrastructure options before provider selection
Comparison snapshot
Against Subscan, OnFinality is the infrastructure choice rather than the indexed explorer API choice. Against QuickNode or Ankr, its Polkadot emphasis is the key reason to keep it in a Polkadot shortlist.
PubFi friction reduction
Coverage Planning
- Source friction
- The fixture maps OnFinality to Polkadot RPC infrastructure and on-chain-state coverage.
- PubFi relief
- Discovery links OnFinality to Polkadot and RPC hubs so teams can request or compare integration without assuming a live PubFi route.
Official source links
Agent-readable resources
Alternatives and hubs
FAQ
What is OnFinality used for?
OnFinality is a candidate source for managed RPC, archive node, and infrastructure-oriented chain data access.