# dRPC | PubFi Discovery

> 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.

Source: Discovery catalog fixtures consumed by the public Discovery routes.
Format: text/markdown; charset=utf-8
Inclusion gate: source.isIndexable is true; draft/noindex records are not emitted as markdown detail pages.
Canonical SEO rule: the HTML detail page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Agent availability rule: raw claim-safe status is preserved for provenance, but actionability uses effective agent availability. Degraded pages require revalidation even when the raw status names a gateway, x402, or MCP surface.

Canonical HTML URL: https://pubfi.ai/discovery/api/drpc
Markdown URL: https://pubfi.ai/discovery/api/drpc.md
Title: dRPC | PubFi Discovery
Provider: dRPC
One-liner: Multichain RPC infrastructure provider for public and high-performance nodes, archive access, and WebSocket RPC workflows.
Long description: 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.
SEO description: dRPC Provider Profile: multichain RPC infrastructure for public and high-performance nodes, archive access, and WebSocket RPC workflows.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Provider Profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Provider Profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: 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 guidance:
- 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.
PubFi gateway route examples: none
Primary keyword: drpc api
Keyword cluster: best_api
Primary chain: multichain
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://drpc.org/
Last verified: 2026-06-11T07:45:00Z
Guardrail: Claim-safe statuses distinguish Provider Profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
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
Auth methods: api key, jwt
REST support: yes
GraphQL support: not listed
WebSocket support: yes
Streaming support: not listed
Webhook support: not listed
Pricing model: freemium
Commercial status: verified (Public free, usage-priced, and enterprise RPC plans)
Free tier: Free plan lists 210M CU/month, public nodes, all available chains, and 100 requests/sec.
Starting price: 6 USD per per 1M requests
Pricing URL: https://drpc.org/pricing
Free rate limit: 100 requests/sec
Paid rate limit: Growth lists 5K requests/sec; enterprise lists unlimited RPS.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://drpc.org/docs
Documentation quality score: not listed
Profile processed at: 2026-06-11T07:45:00Z
Signed off at: 2026-06-11T07:45:00Z
Demand signals: RPC infrastructure source coverage (unproven), on-chain state source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra, On-chain state https://pubfi.ai/discovery/category/on-chain-state
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://drpc.org/
- Provider docs: https://drpc.org/docs
- Official pricing: https://drpc.org/pricing
- PubFi status: fixtures/discovery/public_directory.json#drpc
Alternative APIs:
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective needs_reverification; detail public/markdown-exported)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective needs_reverification; detail public/markdown-exported)
Key facts:
- Primary query: drpc api (source https://drpc.org/docs)
- Primary coverage: RPC endpoints, archive nodes, rate limiting, and WebSocket RPC workflows across supported chains (source https://drpc.org/docs)
- Auth model: dRPC docs include key creation and JWT request authentication topics. (source https://drpc.org/docs)
- Commercial fact: Public pricing lists a Free tier, a Growth usage-priced tier, and Enterprise pricing. (source https://drpc.org/pricing)
- 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 fixtures/discovery/public_directory.json#drpc)
Best for candidates:
- 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
Not ideal for candidates:
- 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
Use case candidates:
- 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
Implementation note metadata:
- auth severity medium
- rate limits severity medium
- coverage severity medium
Quick start metadata: style rest; language http; method POST; path not listed; requires auth yes
Capabilities:
- dRPC API on chain state evidence: requested; auth api_key; procurement not_procurable; coverage arbitrum, base, ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)