# QuickNode JSON-RPC Proxy — Fraxtal Mainnet

> QuickNode JSON-RPC Proxy — Fraxtal 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 Fraxtal mainnet blockchain, enabling queries and interactions with Fraxtal's EVM-compatible L2 network.

## Facts

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

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

Example prompt: What's the latest block number on Fraxtal mainnet? Use eth_blockNumber via the QuickNode Fraxtal mainnet RPC endpoint.

## When to prefer this

Use this endpoint when you need direct RPC access to the Fraxtal mainnet EVM-compatible L2 blockchain — for reading chain state, querying balances, calling contracts, or broadcasting transactions on Fraxtal specifically, as opposed to Ethereum mainnet or other EVM chains.

## 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 results in HTTP 402 Payment Required
- Network congestion may cause timeouts on eth_call or eth_getLogs
- Fraxtal node sync issues may return stale or inconsistent data

## How this service works

JSON-RPC proxy — fraxtal-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested method call — such as block number, account balance, transaction receipt, contract 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-a8533032/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)