PubFiDISCOVERY
Get an API key

Arbitrum data APIs

An Arbitrum data API shortlist should separate RPC, indexed chain-state, and app-specific analytics needs before treating public docs evidence as production-callable coverage. This Discovery hub keeps Arbitrum Provider Profile evidence separate from PubFi gateway certification

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

At a glance

Chain hub summary

Primary query
arbitrum data api
Definition
Automation-approved Discovery sources with coverage targets mapped to arbitrum.
Sources
1
Capabilities
1
Categories
1
Coverage aliases
arbitrum
Last verified
PubFi status
Discovery profile and comparison surface; source pages disclose whether PubFi gateway access is available, requested, or comparison-only.

Official-source citations

dRPC Primary query
drpc api Source
dRPC Primary coverage
RPC endpoints, archive nodes, rate limiting, and WebSocket RPC workflows across supported chains Source
dRPC Auth model
dRPC docs include key creation and JWT request authentication topics. Source
dRPC Commercial fact
Public pricing lists a Free tier, a Growth usage-priced tier, and Enterprise pricing. Source
dRPC 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

Editorial overview

Arbitrum coverage in this batch is anchored by dRPC public documentation evidence. The hub helps teams inspect Arbitrum RPC and chain-state evidence, compare it with Ethereum-adjacent infrastructure providers, and avoid assuming PubFi gateway routing or commercial approval before adapter certification exists.

Start here recommendations

dRPC

Why start here
Start here when the team needs public evidence for dRPC Arbitrum RPC and chain-state documentation while keeping gateway status uncertified.
Best for
Public Arbitrum RPC evidence review

Chain-specific use cases and ecosystem gaps

Chain-specific use cases

  • Inspecting Arbitrum RPC and chain-state documentation before runtime adapter work
  • Comparing Arbitrum support against Ethereum-oriented infrastructure providers
  • Separating public docs evidence from PubFi gateway certification and supplier procurement readiness

Ecosystem gaps

  • Arbitrum API docs often inherit Ethereum assumptions while still needing network-specific endpoint verification.
  • Public docs evidence does not prove account setup, quota, or production-callable PubFi routing.

Coverage entries

Indexed onlyProvider Profile

Multichain RPC infrastructure provider for public and high-performance nodes, archive access, and WebSocket RPC workflows

Provider
dRPC
Page status
Indexable
Agent availability
Provider Profile
Primary category
Rpc Infra
Primary chain
Multichain
RPC infrastructureOn-chain stateMultichain

Matched fixture targets

dRPC API on chain state evidence

Requested
Source
drpc
Auth
Api Key
Procurement
Not Procurable
Coverage
arbitrum, base, ethereum
EthereumBase
chain_state_recordchain_slug, address_or_entity, record_type, captured_at