Skip to main content
Arc exposes standard Ethereum JSON-RPC endpoints — the same HTTP and WebSocket API that Ethereum nodes use — for submitting transactions, querying state, and subscribing to events. Connect through Circle’s primary endpoint or through a third-party node provider.

​
Mainnet endpoints

The primary Circle endpoint (rpc.mainnet.arc.io) accepts anonymous requests with open CORS. No API key or credentials are required. Third-party providers may require their own API key; check each provider’s documentation.
The primary endpoint is load-balanced across multiple backends that may be at slightly different block heights. If you set toBlock to the value returned by eth_blockNumber and a different backend serves the next request, it may return error -32014 because it hasn’t yet imported that block. You can safely retry requests that return -32014 after a brief backoff.

​
Testnet endpoints

​
Network parameters

These parameters identify Arc on the Ethereum network and are required when adding Arc to a wallet or development framework. For wallet configuration instructions using these parameters, see Connect to Arc.

​
Node providers

The following infrastructure partners offer managed RPC access to Arc. Each provider supports HTTP endpoints, and most support WebSocket connections. See Node providers for additional details.

​
Supported methods

Arc supports all standard Ethereum JSON-RPC methods. The following table lists commonly used methods by category. For gas fee parameters and best practices for setting maxFeePerGas, see Gas and fees.
eth_getLogs returns error -32012 when the requested block range exceeds 10,000 blocks. At ~2 blocks/s, 10,000 blocks covers roughly 85 minutes of chain history per call. Log-driven clients must page through history in ≤9,999-block chunks.

​
Troubleshooting