Base data APIs

A Base data API shortlist should separate Ethereum-compatible RPC coverage, indexed state reads, and app-specific analytics before treating public docs evidence as production-callable coverage. This Discovery hub keeps Base 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: base data api
Definition: Automation-approved Discovery sources with coverage targets mapped to base.
Sources: 2
Capabilities: 2
Categories: 1
Coverage aliases: base
Last verified: 2026-06-11
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
Tenderly Primary query: tenderly api Source
Tenderly Primary coverage: Transaction simulation, debugging, monitoring, alerting, and node RPC infrastructure for Web3 teams Source
Tenderly Free plan boundary: Public pricing says Tenderly Free includes browser UI access and no API access on Free. Source
Tenderly Commercial fact: Public pricing describes Console and infrastructure features, with capacity, support, and chain count sized in conversation. Source
Tenderly PubFi status: PubFi Discovery tracks Tenderly as a public Provider Profile only; this profile does not assert a PubFi gateway route, adapter certification, or credential availability. Source

Editorial overview

Base coverage in this batch is anchored by dRPC public documentation evidence. The hub gives teams a claim-safe place to inspect Base API evidence and compare nearby EVM infrastructure options before any runtime adapter, credential, or commercial approval work begins.

Start here recommendations

dRPC

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

Chain-specific use cases and ecosystem gaps

Chain-specific use cases

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

Ecosystem gaps

Base support often appears inside broader EVM documentation and still needs route-level verification.
Public docs evidence does not prove account setup, quota, or production-callable PubFi routing.