Calling RPCX Methods

Call a saved RPCX method as rpcx_<name> at rpcx.mainnet.solana.nolimitnodes.com with your NoLimitNodes API key and read the result.

A saved method is a JSON-RPC method. Call it as rpcx_<name> at https://rpcx.mainnet.solana.nolimitnodes.com, with your NoLimitNodes API key in the x-api-key header. It is the same API key you use for your RPC endpoint.

Request

Pass params as an object of named values, with the names from the method header. A positional array is rejected. This call runs the txsFor method from the quickstart for two wallets:

curl https://rpcx.mainnet.solana.nolimitnodes.com \  -H "Content-Type: application/json" \  -H "x-api-key: $NLN_API_KEY" \  -d '{    "jsonrpc": "2.0",    "id": 1,    "method": "rpcx_txsFor",    "params": {      "wallets": [        "ARu4n5mFdZogZAravu7CcizaojWnS6oqka37gdLT5SZn",        "EKmzDJWkajsqLMkY5WLWts9iUgqHCQny6hhd77fcQGN"      ],      "from": "2026-11-15T12:00:00Z",      "to": "2026-11-15T13:00:00Z"    }  }'

Leave out a param that has a default to use the default. Leave out an optional param without a default (name?: type), or pass null, and the method sees null. A method without params takes "params": {}, or no params field at all. A time param takes RFC 3339 or YYYY-MM-DD, in UTC. A list param, such as pubkey[], takes a JSON array of up to 1,000 values.

Pass every address in one call. RPCX reads them together, so one call with 500 wallets is much faster than 500 calls with one wallet.

Response

{  "jsonrpc": "2.0",  "id": 1,  "result": {    "rows": [      { "address": "ARu4n5mFdZogZAravu7CcizaojWnS6oqka37gdLT5SZn", "sig": "2bZ38WCx2c6kyf7GFpnviH8TtbBJbGwvscaUiojjLYk6THFg2aNA6fh2cPDgyGdK8uwUQc6iFgk4VMUKtPTbRRVm", "slot": 380112345, "ts": "2026-11-15 21:04:11.000", "success": true, "fee": 5000, "signer": "ARu4n5mFdZogZAravu7CcizaojWnS6oqka37gdLT5SZn" }    ],    "cu": 3,    "sources": ["lite_rpc"]  }}

The row above is shortened: a real live_transactions row has every column of the table.

FieldMeaning
rowsThe result, one object per row
cuCompute units this call cost
sourcesThe live sources the run read. For information only.

A call returns up to 10,000 rows. A result with more rows fails with -32002, limit_exceeded, so end the method with take or narrow its filter. For larger results, use Export in the dashboard, which returns up to 5,000,000 rows.

Batches

Send an array of up to 100 calls. RPCX runs them one after another, in order, and checks the budget before each one. When the minute's budget runs out, the remaining calls fail with -32003. When the month's allowance and your bought CU run out, the remaining calls fail with -32007. Only rpcx_ methods are served at this address, so send other Solana methods to your RPC endpoint.

A call without an id is a notification: it runs and is billed, but gets no response.

Errors

Errors use the standard JSON-RPC error object with HTTP status 200. A param with the wrong type fails with -32602:

{  "jsonrpc": "2.0",  "id": 1,  "error": {    "code": -32602,    "message": "invalid params: param `from` must be an RFC 3339 timestamp or a YYYY-MM-DD date (UTC), got \"yesterday\""  }}

When your plan's allowance for the month and your bought CU are both used up, a call fails with -32007:

{  "jsonrpc": "2.0",  "id": 1,  "error": {    "code": -32007,    "message": "Your plan's RPCX allowance for this month is used up and you have no CU left. Buy CU on the RPCX page to keep going, or wait for the allowance reset on 2026-12-01 UTC."  }}

Buy CU in the RPCX page, or wait for the date in the message. See Plan allowance and bought CU.

See Errors, limits, and billing for every code.

Versions

A call always runs the active version of the method. Saving the same name again from the dashboard creates a new version, and the next call uses it.