Base RPC Endpoint Documentation | ERPC
Base RPC Endpoint Documentation
Use ERPC as your Base RPC endpoint for HTTP JSON-RPC requests and WebSocket subscriptions. Base RPC is part of ERPC's RPC APIs within our Global Edge Blockchain Infrastructure, and the API key can be managed from the ERPC Web Dashboard.
You can use the same RPC key as Solana, Ethereum, and Avalanche.
Please add your API key to the
api-key parameter.Endpoints
Send JSON-RPC 2.0 requests as HTTP POST to:
text
https://base.erpc.global?api-key=<YOUR_API_KEY>https://base.erpc.global?api-key=<YOUR_API_KEY>For subscriptions, connect over WebSocket to:
text
wss://base.erpc.global?api-key=<YOUR_API_KEY>wss://base.erpc.global?api-key=<YOUR_API_KEY>Requests are accepted at
/ only.Examples
Here is an HTTP request example.
bash
curl 'https://base.erpc.global?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
"jsonrpc":"2.0","id":1,
"method":"eth_blockNumber"
}'curl 'https://base.erpc.global?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
"jsonrpc":"2.0","id":1,
"method":"eth_blockNumber"
}'You can obtain and check your API key on the ERPC Web Dashboard: ERPC Web Dashboard
Batch Requests
JSON-RPC batches of up to 256 calls per HTTP request are supported. Each call in a batch is metered as its own call.
Usage Metering
Usage is metered in tokens per JSON-RPC call. Each entry in an HTTP batch and each JSON-RPC call sent over a WebSocket connection is metered separately.
Free Plan Limits
On the Free plan, your account can send one request per 10 seconds. The limit is counted per account, not per endpoint, so a request to another chain can also count toward it. A request sent sooner is answered with HTTP
429, and the retry-after header gives the wait in seconds.On the Free plan, a request that carries two or more JSON-RPC calls is answered with HTTP
429, and none of its calls is sent: each call gets a JSON-RPC error with code -32041. Send these calls one at a time instead.On the Free plan, WebSocket connections are not available and are answered with HTTP
403.Supported Methods
Base is EVM-compatible and uses the same JSON-RPC methods as Ethereum. ERPC does not apply a fixed method allowlist to the Base endpoint. For the Ethereum method families, see the Ethereum RPC Endpoint Documentation.
Response Status Codes
| HTTP status | Meaning |
|---|---|
| 200 | Upstream JSON-RPC response. |
| 400 | Missing API key, Invalid JSON-RPC request, or JSON-RPC batch exceeds 256 calls. |
| 401 | Unauthorized API KEY. |
| 403 | A WebSocket connection on the Free plan. |
| 404 | A path other than /. |
| 429 | Rate limited, including the Free plan limits above: more than one request per 10 seconds, or two or more calls in one request. The retry-after header gives the wait in seconds. |
| 502 | The upstream RPC request could not be completed. |
| 503 | The service is temporarily unavailable. |
WebSocket connections use
101 (protocol upgrade accepted) in addition to the codes above.Base RPC Methods and Documentation
For the full list of standard methods, parameters, and specifications, please refer to the official documentation.