# QuickNode JSON-RPC Proxy — TON Mainnet

> QuickNode JSON-RPC Proxy — TON 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-14).

Proxies JSON-RPC calls to the TON (The Open Network) mainnet blockchain via QuickNode's infrastructure

## Facts

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

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

Example prompt: Use QuickNode's TON mainnet RPC to get the latest masterchain block info — call the getLastMasterchainBlock method with no params and jsonrpc 2.0.

## When to prefer this

Choose this endpoint when you need to interact specifically with the TON (The Open Network) mainnet blockchain — querying account balances, fetching blocks, reading smart contract state, or broadcasting transactions on TON. Use this over Ethereum or other chain endpoints when the target network is TON.

## 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 results in 402 Payment Required
- Network congestion or TON node unavailability may cause timeout or 503 errors
- Requesting non-existent blocks or addresses returns null result

## How this service works

JSON-RPC proxy — ton-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested TON blockchain method call, which may include block headers, account states, transaction records, smart contract outputs, 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-ae9a21f6/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)