# Pocket Network Celo Mainnet JSON-RPC

> Pocket Network Celo Mainnet JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-03).

Provides read-only Ethereum-compatible JSON-RPC access to Celo mainnet (an OP-Stack L2) via Pocket Network's decentralised node supplier set, billed per-request in USDC.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/celo?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-celo-mainnet-json-rpc-139e527d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cKP-VmoakLscF1QlQEzoi

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 pocket-network-celo-mainnet-json-rpc-139e527d -d '<json body>'
```

Example prompt: What's the current CELO balance of wallet address 0x1234...abcd on Celo mainnet? Use eth_getBalance to check it.

## When to prefer this

Choose this endpoint when you need permissionless, key-free read access to Celo mainnet (an OP-Stack L2) without creating an account, paying only $0.005 USDC per call via x402. Prefer it over centralised RPC providers when censorship-resistance and decentralisation matter, or when you want to avoid API key management. Not suitable for write operations or Celo Alfajores testnet.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (Method not found)
- Malformed params returns error code -32602 (Invalid params)
- Write methods (eth_sendRawTransaction) rejected — endpoint is read-only
- Payment failure or insufficient USDC balance returns HTTP 402
- Rate limit or node unavailability returns HTTP 503 or timeout
- Querying non-existent block/tx hash returns null result

## How this service works

Read-only JSON-RPC access to Celo mainnet, now an OP-Stack L2, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

## Output

A standard Ethereum JSON-RPC response object containing the 'result' field with requested blockchain data (balance in wei, block object, transaction receipt, logs array, gas estimate, etc.) or an 'error' object with code and message if the call fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "debug_getBadBlocks",
    "debug_getRawBlock",
    "debug_getRawHeader",
    "debug_getRawReceipts",
    "debug_getRawTransaction",
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_config",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockAccessList",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "eth_getStorageValues",
    "eth_getTransactionByBlockHashAndIndex",
    "eth_getTransactionByBlockNumberAndIndex",
    "eth_getTransactionByHash",
    "eth_getTransactionCount",
    "eth_getTransactionReceipt",
    "eth_getUncleByBlockHashAndIndex",
    "eth_getUncleByBlockNumberAndIndex",
    "eth_getUncleCountByBlockHash",
    "eth_getUncleCountByBlockNumber",
    "eth_maxPriorityFeePerGas",
    "eth_newBlockFilter",
    "eth_newFilter",
    "eth_newPendingTransactionFilter",
    "eth_simulateV1",
    "eth_syncing",
    "eth_uninstallFilter",
    "net_listening",
    "net_peerCount",
    "net_version",
    "txpool_status",
    "web3_clientVersion",
    "web3_sha3"
   ],
   "description": "JSON-RPC read method, e.g. eth_getBalance"
  },
  "params": {
   "description": "Parameters per the Ethereum JSON-RPC spec"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": 1,
   "result": false,
   "jsonrpc": "2.0"
  },
  "portal": {
   "serviceId": "celo",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-celo-mainnet-json-rpc-139e527d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)