---
title: "Arc RPC Endpoint Documentation"
description: "Use ERPC as your Arc Network RPC endpoint for HTTP JSON-RPC requests."
canonical: "https://erpc.global/en/doc/arc-rpc/general/"
locale: "en"
---

# Arc RPC Endpoint Documentation

## Arc RPC Endpoint Documentation

Use ERPC as your Arc™ RPC endpoint for HTTP JSON-RPC requests. Arc 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.

Pass your API key in the `api-key` query parameter, or send it as `Authorization: Bearer <YOUR_API_KEY>`. When both are present, the query parameter is used.

### Endpoints

Send JSON-RPC 2.0 requests as HTTP POST to:

```text
https://edge.erpc.global/arc?api-key=<YOUR_API_KEY>
```

or the dedicated host:

```text
https://arc.erpc.global?api-key=<YOUR_API_KEY>
```

Requests are accepted at `/` only.

### Examples

Here is an HTTP request example with the API key in the query parameter.

```bash
curl 'https://edge.erpc.global/arc?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
  "jsonrpc":"2.0","id":1,
  "method":"eth_blockNumber"
}'
```

Here is the same request with the API key in the `Authorization` header.

```bash
curl 'https://edge.erpc.global/arc' --header 'Content-Type: application/json' --header 'Authorization: Bearer <YOUR_API_KEY>' --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](https://dashboard.erpc.global/en)

### Batch Requests

JSON-RPC batches of 1 to 100 calls per HTTP request are supported. Every call needs its own `id`, and `id` values must not repeat within a batch. Each call in a batch is metered as its own call. The request body can be up to 1 MiB.

### Usage Metering

Usage is metered in tokens, and the token rate can differ by method. Each call in an HTTP batch 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.

### Supported Methods

The endpoint serves these 38 methods, grouped by namespace.

- `eth_*` (24): `eth_blockNumber`, `eth_call`, `eth_chainId`, `eth_estimateGas`, `eth_feeHistory`, `eth_gasPrice`, `eth_getBalance`, `eth_getBlockByHash`, `eth_getBlockByNumber`, `eth_getBlockReceipts`, `eth_getBlockTransactionCountByHash`, `eth_getBlockTransactionCountByNumber`, `eth_getCode`, `eth_getLogs`, `eth_getProof`, `eth_getStorageAt`, `eth_getTransactionByBlockHashAndIndex`, `eth_getTransactionByBlockNumberAndIndex`, `eth_getTransactionByHash`, `eth_getTransactionCount`, `eth_getTransactionReceipt`, `eth_maxPriorityFeePerGas`, `eth_sendRawTransaction`, `eth_syncing`
- `net_*` (3): `net_listening`, `net_peerCount`, `net_version`
- `web3_*` (2): `web3_clientVersion`, `web3_sha3`
- `txpool_*` (3): `txpool_content`, `txpool_inspect`, `txpool_status`
- `debug_*` (4): `debug_traceBlockByHash`, `debug_traceBlockByNumber`, `debug_traceCall`, `debug_traceTransaction`
- `trace_*` (2): `trace_block`, `trace_transaction`

A method or path that is not listed is answered with HTTP `400`.

### Response Status Codes

| HTTP status | Meaning |
| --- | --- |
| 200 | Upstream JSON-RPC response. A JSON-RPC error is also returned with HTTP `200`: it keeps the request `id` and `error.code`, its `error.message` is `ERPC upstream error`, and `error.data` is not returned. |
| 400 | A method or path outside the Supported Methods list, an invalid JSON-RPC request, an empty batch or a batch over 100 calls, a duplicate `id` in a batch, or a body over 1 MiB. |
| 401 | Missing or invalid API key, or an IP or Origin restriction on the key is not met. |
| 405 | A request method other than POST. |
| 426 | A WebSocket Upgrade was requested. The endpoint is HTTP only. |
| 429 | Rate limited, including the Free plan limits above: more than one request per 10 seconds, or two or more calls in one request. If a `retry-after` header is present, wait that many seconds. |
| 502 | The upstream request could not be completed: a failed upstream response, a response over 8 MiB, or no answer within 30 seconds. |
| 503 | The service is temporarily unavailable. |

### Arc RPC Methods and Documentation

The Arc documentation describes the standard Ethereum JSON-RPC methods on Arc and links to the reference for their parameters. A method missing from the list above is answered with HTTP `400`, even if the Arc documentation lists it.

[https://docs.arc.io/arc/references/rpc-endpoints](https://docs.arc.io/arc/references/rpc-endpoints)

Arc is a trademark of Circle Internet Group, Inc. and/or its affiliates.
