# Phantom API — Celo RPC Endpoint

> Phantom API — Celo RPC Endpoint is a paid API for AI agents from phantom-api-omega.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Provides JSON-RPC access to the Celo blockchain network, enabling read and write operations against Celo nodes via standard Ethereum-compatible RPC methods.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/celo/rpc
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-celo-rpc-endpoint-12a2e99b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hXpMveL-_ffKnbRi4J91x

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 phantom-api-celo-rpc-endpoint-12a2e99b -d '<json body>'
```

Example prompt: Can you check the current CELO balance of wallet address 0xAbc123... on the Celo network using eth_getBalance with the latest block?

## When to prefer this

Choose this endpoint when you need direct JSON-RPC access to the Celo blockchain specifically, and want a pay-per-call model without monthly subscription commitments. Prefer over self-hosted nodes when you lack infrastructure, and over general EVM RPC providers when you need Celo-native support with guaranteed uptime via a managed service.

## Known failure modes

- Invalid 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
- Network congestion or node unavailability returns HTTP 503 or timeout
- Unsupported Celo-specific methods may return not-implemented errors

## How this service works

Lightning-fast access to blockchain data, smart contract insights, and Web3 infrastructure across 57+ networks. Pay-per-call via x402.

## Output

A standard JSON-RPC response object containing an 'id', 'jsonrpc' version field, and a 'result' field with the blockchain data requested (e.g. hex-encoded balance, block object, transaction receipt, or log array). On error, returns an 'error' object with code and message.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array",
   "items": {}
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-celo-rpc-endpoint-12a2e99b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phantom-api-omega.vercel.app](https://www.zero.xyz/host/phantom-api-omega.vercel.app/llms.txt)