# QuickNode JSON-RPC Proxy — XRPL EVM Testnet

> QuickNode JSON-RPC Proxy — XRPL EVM Testnet 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 testnet blockchain node via QuickNode infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/xrplevm-testnet/
- 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-e0e27671
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_K_ggXB8d0u9lfXG2YPbqO

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-e0e27671 -d '<json body>'
```

Example prompt: Call eth_getBalance on the XRPL EVM testnet for address 0xAbC123...def456 using QuickNode's RPC proxy — I want to see the current testnet ETH balance in wei.

## When to prefer this

Choose this endpoint when you specifically need to interact with the XRP Ledger EVM-compatible testnet — for testing smart contracts, validating transactions, or querying testnet state before deploying to mainnet. Prefer this over generic Ethereum RPC endpoints when your target chain is xrplevm-testnet. Use for development, QA, and staging workflows involving the XRPL EVM ecosystem.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 Method not found
- Malformed params array returns error code -32602 Invalid params
- Payment not provided or insufficient USDC (requires $10 per call) results in 402 Payment Required
- Network congestion or node unavailability returns HTTP 503 or timeout
- Calling mainnet-specific addresses or contracts that don't exist on testnet returns null or zero result
- Rate limiting if payment flow fails mid-request

## How this service works

JSON-RPC proxy — xrplevm-testnet

## Output

Returns a standard JSON-RPC 2.0 response object with an 'id' matching the request, a 'jsonrpc' field set to '2.0', and either a 'result' field containing the method-specific return value (e.g. hex-encoded block number, balance, transaction receipt, contract output) or an 'error' object with code and message fields if the call fails.

## 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-e0e27671/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)