Beam

Docs

Beam speaks standard Ethereum JSON-RPC over HTTPS. If your tooling works with any EVM endpoint, it works here.

Connect

In a wallet, add Arc as a custom network with chain ID 5042 (0x13b2), currency USDC and the RPC URL below. The home page has a one-click button and a manual setup table.

Latency-sensitive? https://direct.beamrpc.com is the same endpoint without the Cloudflare hop in front of it.

WebSocket subscriptions (eth_subscribe for newHeads and logs) are available at wss://rpc.beamrpc.com.

RPC URL
https://rpc.beamrpc.com
Chain ID
5042 · 0x13b2
Currency
USDC · 18 decimals
Block time
~500 ms

curl

curl -s https://rpc.beamrpc.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

ethers v6

import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider("https://rpc.beamrpc.com", 5042);
const block = await provider.getBlockNumber();

Foundry

cast block-number --rpc-url https://rpc.beamrpc.com

Rate limits

300 requests/second per IP, burst-friendly. Short bursts above that are tolerated; sustained excess returns HTTP 429. There are no API keys and no tiers. If you need more for a production app, back off and retry with jitter rather than fanning out across IPs.

Supported methods

Standard eth_, net_ and web3_ read methods, plus eth_sendRawTransaction for broadcasting signed transactions. JSON-RPC batches are accepted, up to 100 calls per request.

The pending-pool (txpool_*), debug_*, trace_* and admin_* namespaces are not exposed. Calls to them return JSON-RPC error -32601 (method not available).

CORS, keys and privacy

  • CORS is enabled for every origin, so browser dApps can call the endpoint directly.
  • No API key or signup. The URL is the whole integration.
  • No cookies, no analytics, no stored IP addresses or request bodies; only aggregate counts. The privacy page lists exactly what is and is not kept.
  • The endpoint is free to use. It is an independent, third-party service and is not affiliated with Circle.

Status

Live block height, lag behind the network, uptime and request counts are on the status page. The same data is available as JSON at https://rpc.beamrpc.com/status.

If the node falls behind the network head, the status page shows the lag in blocks so you can decide whether to wait or fail over.