PubFiDISCOVERY
Get an API key

API profile

dRPC

dRPC is tracked as a multichain RPC infrastructure Provider Profile. Public docs cover RPC onboarding, key creation, rate limiting, archive nodes, and method documentation; PubFi Discovery does not assert a PubFi gateway route or adapter certification for dRPC

Coming soonNeeds re-verification
RPC infrastructureOn-chain stateMultichain
Official siteReverify source evidence

Decision guide

Use it when

Teams comparing multichain RPC infrastructure providers

Check first

Market-data normalization that does not need direct chain RPC

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, JWT
Pricing
Freemium
Agent actionability
Editorial revalidation required; runtime status separate
PubFi gateway
Live Registry unavailable
Last verified

Provider-sourced facts

Primary query
drpc api Source
Primary coverage
RPC endpoints, archive nodes, rate limiting, and WebSocket RPC workflows across supported chains Source
Auth model
dRPC docs include key creation and JWT request authentication topics. Source
Commercial fact
Public pricing lists a Free tier, a Growth usage-priced tier, and Enterprise pricing. Source
PubFi status
PubFi Discovery tracks dRPC as a public Provider Profile only; this profile does not assert a PubFi gateway route, adapter certification, or credential availability. Source

Best fit and tradeoffs

Best for

  • Teams comparing multichain RPC infrastructure providers
  • Backend workloads that need high RPS, archive-node access, or WebSocket RPC
  • RPC buyer research that needs public pricing and rate-limit facts
  • They want a public starting point for evaluating dRPC API documentation.
  • They need to compare dRPC against nearby crypto data providers before runtime integration work.
  • They want claim-safe evidence that can be promoted later when adapter certification exists.

Watchouts

  • Market-data normalization that does not need direct chain RPC
  • Teams expecting a PubFi-certified gateway route today
  • Workloads that cannot manage provider account keys or JWT-based authentication
  • Automation-built profiles may have incomplete category, pricing, quota, or endpoint coverage until deeper docs parsing runs.
  • Public docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, and terms before treating the provider as production-callable.

Why teams choose it

dRPC API is an automation-built Provider Profile based on public API corpus evidence. It helps teams inspect dRPC docs, product naming, and on chain state fit before any runtime adapter or commercial approval work begins.

Discovery keeps this page claim-safe: inclusion means public evidence was processed into a Provider Profile, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, or supplier procurement for dRPC.

What it can cover

dRPC API on chain state evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Ethereum, Arbitrum, Base
Output contracts
Chain State Record

Quick start

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

PubFi gateway

Live Registry unavailable

PubFi could not verify the active signed Registry generation. Checked-in Discovery content is not execution authority, so this page fails closed instead of inferring a gateway route.

Runtime status
registry_unavailable
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Retry the live Registry view or inspect the runtime OpenAPI before execution.
  • Do not infer availability from provider documentation, product copy, or repository data.

Reference details

Access

Auth methods
API key, JWT
Pricing model
Freemium
Free tier
Free plan lists 210M CU/month, public nodes, all available chains, and 100 requests/sec.
Starting price
6 USD per 1M requests
Pricing source
Official pricing
Free rate limit
100 requests/sec
Paid rate limit
Growth lists 5K requests/sec; enterprise lists unlimited RPS.

Data shape

Data types
Drpc.Org Docs Arbitrum Api, Drpc.Org Docs Avalanche Api, Drpc.Org Docs Bitcoin Api, Drpc.Org Docs Bsc Api, Drpc.Org Docs Cosmos Api Chaininfo Status, Drpc.Org Docs Ethereum Api, Drpc.Org Docs Optimism Api, Drpc.Org Docs Polygon Api
Protocols
REST, WebSocket
REST support
Yes
GraphQL support
Not listed
WebSocket support
Yes
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
Degraded
Editorial posture
Needs re-verification

Implementation notes

Docs

Medium

Review dRPC public docs and authentication requirements before any adapter certification work starts.

Coverage

Medium

Treat the current dRPC API profile as processed evidence, not as complete coverage of every chain, endpoint, or product surface.

Schema

Low

Use endpoint-specific docs evidence before deriving runtime request or response contracts.

Use cases

  • Compare dRPC with QuickNode, Ankr, and Alchemy for multichain RPC coverage
  • Evaluate free versus paid RPS needs for JSON-RPC workloads
  • Plan archive-node and WebSocket access without assuming PubFi gateway availability

Comparison snapshot

dRPC API should be compared with providers that cover similar on chain state workflows. The current automation output is enough for Discovery visibility and follow-up triage, but not for certified gateway routing.

PubFi friction relief

Docs

Source friction
dRPC public docs were captured in the public documentation evidence.
PubFi relief
PubFi Discovery turns the public evidence into a claim-safe Provider Profile and separates it from gateway certification.

FAQ

What is dRPC used for?

dRPC is used for multichain RPC endpoint access, including public nodes, high-performance nodes, archive-node workloads, and WebSocket RPC integrations.

Does dRPC require authentication?

Yes for managed project usage. Public docs include key creation and JWT request authentication topics, so Discovery treats auth as part of implementation planning.

Is dRPC available through the PubFi gateway?

No. This page is a public Provider Profile and does not claim a PubFi gateway route, adapter certification, or upstream credential.