PubFiDISCOVERY
Get an API key

API profile

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 soonNeeds re-verification
RPC infrastructureOn-chain statePolkadot
Official siteReverify source evidence

Decision guide

Use it when

Polkadot RPC and archive access

Check first

Standalone market price datasets

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 coverage
Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks Source
Fixture coverage
RPC infrastructure and on-chain state coverage for the Polkadot fixture target Source

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.

What it can cover

OnFinality RPC infrastructure coverage

Current
Category
RPC infrastructure
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Polkadot
Output contracts
Rpc Endpoint Status

OnFinality 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
curl
Language
curl
Method
POST
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

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
Developer plan includes 400,000 RPC response units/day and up to 40 response units/sec.
Starting price
$49 / month
Pricing source
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

Data shape

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

Public evidence

Documentation
Provider docs
Status page
Provider status
Source coverage status
Degraded
Editorial posture
Needs re-verification

Implementation notes

Coverage

High

Confirm the target Polkadot network, archive requirement, and method set before treating OnFinality as interchangeable with generic Ethereum RPC providers.

Rate limits

Medium

Use response-unit limits rather than raw request counts when planning workload size from the public commercial fixture.

Auth

Medium

Plan for API-key or endpoint credential handling separately from PubFi source discovery because this profile does not claim universal gateway access.

Use cases

  • 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 relief

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.

FAQ

What is OnFinality used for?

OnFinality is a candidate source for managed RPC, archive node, and infrastructure-oriented chain data access.