# QuickNode JSON-RPC Proxy — Celo Mainnet

> QuickNode JSON-RPC Proxy — Celo 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 Celo mainnet blockchain, enabling queries and interactions with Celo network nodes via standard Ethereum-compatible RPC methods.

## Facts

- Endpoint: POST https://x402.quicknode.com/celo-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-866a21eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kx1_z2AT--CEPHlM_z567

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

Example prompt: Call eth_getBalance on Celo mainnet for address 0x1234567890abcdef1234567890abcdef12345678 at block latest and tell me the balance in CELO.

## When to prefer this

Use this endpoint when you need to interact with the Celo mainnet blockchain specifically, particularly when other free RPC endpoints are rate-limited or unavailable and you are willing to pay per call. Ideal for agents needing reliable, low-latency access to Celo chain data or smart contract calls without managing 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 provided or insufficient USDC returns 402 Payment Required
- Rate limiting or node unavailability returns 503 or timeout
- Unsupported method for Celo-specific chain returns error response

## How this service works

JSON-RPC proxy — celo-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g., block data, balance in hex, transaction receipt, contract return value) or an error object with code and message if the call fails.

## 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-866a21eb/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)