# QuickNode JSON-RPC Proxy — Vana Moksha Testnet

> QuickNode JSON-RPC Proxy — Vana Moksha 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-13).

Proxies JSON-RPC calls to the Vana Moksha testnet blockchain network via QuickNode's infrastructure

## Facts

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

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

Example prompt: Can you call eth_blockNumber on the Vana Moksha testnet using QuickNode's RPC and tell me the latest block number?

## When to prefer this

Use this endpoint when you need to interact specifically with the Vana Moksha testnet blockchain via standard JSON-RPC methods. Prefer this over other QuickNode endpoints when your target chain is Vana Moksha (not Ethereum, Cosmos, NEAR, or other chains). Suitable for reading blockchain state, submitting transactions, or calling smart contracts on Vana's testnet environment.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code -32601
- Malformed params array causes parse or invalid params error
- Network unavailable on Vana Moksha testnet returns connectivity error
- Payment of $10 USDC not provided causes 402 Payment Required
- Rate limiting or quota exceeded returns 429-equivalent error

## How this service works

JSON-RPC proxy — vana-moksha

## Output

Returns a standard JSON-RPC 2.0 response object with an id, jsonrpc version string, and result field containing the blockchain data requested (e.g. block number, transaction receipt, call return value) 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-aa14b7e0/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)