# QuickNode XRP Mainnet JSON-RPC Proxy

> QuickNode XRP Mainnet JSON-RPC Proxy 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 mainnet, enabling blockchain queries and transactions via standard JSON-RPC 2.0 protocol

## Facts

- Endpoint: POST https://x402.quicknode.com/xrp-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-7a6dfc76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9Odede64ZQ7DmgdG1l1Mr

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

Example prompt: Use the XRP mainnet JSON-RPC endpoint to call account_info with account r3AdW6pNvtm9vPNHFngc1ZnzrhVwM5YLKB and get the current XRP balance and sequence number.

## When to prefer this

Use this endpoint when you need programmatic access to the XRP Ledger mainnet via standard JSON-RPC — particularly when other XRP node access is unavailable, you need a pay-per-call model without subscription overhead, or you want QuickNode-grade reliability for production XRP queries.

## Known failure modes

- Invalid JSON-RPC method name returns error response with code -32601
- Malformed params array causes parse or invalid request error
- Insufficient USDC payment ($10 required per call) results in 402 Payment Required
- Network or node unavailability returns a server error
- Invalid account address format returns ledger-specific error

## How this service works

JSON-RPC proxy — xrp-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested XRP Ledger method call, which may include account balances, transaction records, ledger metadata, or other on-chain data depending on the method invoked.

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