# QuickNode JSON-RPC Proxy — XRP Ledger EVM Mainnet

> QuickNode JSON-RPC Proxy — XRP Ledger EVM Mainnet is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-15).

Proxies JSON-RPC calls to the XRP Ledger EVM-compatible mainnet blockchain node via QuickNode infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/xrplevm-mainnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-b5259c3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ta9WI_gmVqrY7dlPZfLrf

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quicknode-b5259c3e -d '<json body>'
```

Example prompt: Call eth_blockNumber on the XRP Ledger EVM mainnet via QuickNode so I can see the current block height of the XRPLEVM chain.

## When to prefer this

Use this endpoint when you need direct JSON-RPC access to the XRP Ledger EVM-compatible mainnet, such as reading smart contract state, querying balances, fetching blocks or transactions, or broadcasting signed transactions on the XRPLEVM network. Prefer over generic Ethereum RPC endpoints when specifically targeting XRPLEVM mainnet.

## Known failure modes

- Invalid JSON-RPC method returns error code -32601
- Malformed params array returns -32602 invalid params error
- Payment not provided or insufficient returns 402 Payment Required
- Network congestion or node unavailability returns 503 or timeout
- Invalid address or hash format returns -32000 or execution revert

## How this service works

JSON-RPC proxy — xrplevm-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object with the result field containing the blockchain data requested (e.g. block number, transaction hash, contract return value, account balance) or an error object if the call failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "jsonrpc",
  "method"
 ],
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ],
   "description": "Request identifier"
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
  },
  "params": {
   "type": "array",
   "description": "Method parameters"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "error": {
   "type": "object",
   "properties": {
    "code": {
     "type": "integer"
    },
    "message": {
     "type": "string"
    }
   }
  },
  "result": {
   "description": "RPC result (type varies by method)"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-b5259c3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quicknode.com](https://www.zero.xyz/host/x402.quicknode.com/llms.txt)