# QuickNode JSON-RPC Proxy — Fantom Mainnet

> QuickNode JSON-RPC Proxy — Fantom 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 Fantom mainnet blockchain, enabling queries and interactions with on-chain data via standard Ethereum-compatible RPC methods.

## Facts

- Endpoint: POST https://x402.quicknode.com/fantom-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-45a4aeaf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D8wA89fYueWTfp48D-5Ve

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

Example prompt: Call eth_getBalance on Fantom mainnet for wallet address 0xAbC123... and tell me the current FTM balance.

## When to prefer this

Use this endpoint when you need direct, low-latency JSON-RPC access to Fantom mainnet specifically — querying balances, calling contracts, fetching blocks, or broadcasting transactions on the FTM/Opera chain. Prefer over generic Web3 providers when you need a pay-per-call model without subscription overhead and when Fantom (not Ethereum or other EVM chains) is the target network.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code -32601
- Malformed params array causes -32602 invalid params error
- Payment of $10 USDC not provided results in HTTP 402 Payment Required
- Network congestion or node unavailability returns 503 or timeout
- Calling a method unsupported on Fantom returns method not supported error

## How this service works

JSON-RPC proxy — fantom-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g., block number, balance in hex, transaction receipt, call return data) 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-45a4aeaf/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)