Docs
PricingDashboard

Documentation

Getting started

Create an endpoint in the dashboard and send JSON-RPC to a managed full node.

1. Create an endpoint

Sign up on RpcNode, pick a network and environment — you get an endpoint UUID.

Open dashboard

2. Endpoint URL

The HTTPS JSON-RPC URL is built from network slug, environment, and endpoint UUID — same values as in the dashboard (e.g. ethereum + mainnet).

Pattern

https://{network}-{environment}.rpcnode.dev/{endpoint-uuid}

Example

https://ethereum-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7

3. First request

Send a standard JSON-RPC 2.0 POST with Content-Type: application/json.

curl example

curl https://ethereum-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7 \
  -X POST \
  -H 'content-type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_blockNumber",
  "params": []
}'

Rate limits (RPS)

Each endpoint has a requests-per-second (RPS) limit from your plan. When exceeded, the gateway returns HTTP 429 with JSON-RPC error code -32005.

The counter is per endpoint and resets every Unix second (a fixed 1-second window). Your limit is shown in the dashboard and on the pricing page.

Requests rejected for RPS do not consume credits and are not counted in usage statistics.

Example response

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32005,
    "message": "rps limit exceeded"
  }
}

IP allowlist — Restrict which client IPs can call an endpoint. An empty list allows all IPs; a non-empty list allows only the addresses you add.

Networks & methods

Use the left nav for networks and RPC methods. Credits come from the billing API; parameter docs from the content catalog.