# QuickNode JSON-RPC Proxy — Fuel Mainnet

> QuickNode JSON-RPC Proxy — Fuel 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-15).

Proxies JSON-RPC calls to the Fuel blockchain mainnet, enabling agents to query chain state, submit transactions, and interact with smart contracts on Fuel.

## Facts

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

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

Example prompt: Call the Fuel mainnet RPC to get the latest block number — use the fuel_latestBlock method with no params.

## When to prefer this

Choose this endpoint when you need to interact specifically with the Fuel mainnet blockchain via standard JSON-RPC. Prefer this over generic Ethereum RPC endpoints when targeting Fuel-native smart contracts, accounts, or transactions. Use when you need a reliable, low-latency node provider for Fuel without running your own node.

## 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 included or insufficient returns HTTP 402 Payment Required
- Network congestion or node unavailability returns HTTP 503 or timeout
- Invalid jsonrpc version (not '2.0') may be rejected

## How this service works

JSON-RPC proxy — fuel-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method call (e.g. block data, transaction details, contract return values) or an error object with code and message 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-22293897/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)