# Phantom API — ApeChain RPC Endpoint

> Phantom API — ApeChain 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-10-20).

Provides a pay-per-call JSON-RPC gateway to the ApeChain blockchain network, enabling on-chain data queries and smart contract interactions.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/apechain/rpc?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-apechain-rpc-endpoint-b61b8775
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GSrw36c_H2lsXEK9sCmYc

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-apechain-rpc-endpoint-b61b8775 -d '<json body>'
```

Example prompt: Can you fetch the current block number on ApeChain using an eth_blockNumber RPC call?

## When to prefer this

Choose this endpoint when you specifically need to interact with the ApeChain network (APE's Layer 2 / dedicated chain) and want a pay-per-call model without subscription commitments. Prefer it over general-purpose RPC providers when your agent needs metered, micropayment-based access to ApeChain specifically, or when integrating x402 payment flows.

## Known failure modes

- Invalid or unsupported RPC method name returns an error response
- Malformed params array causes a parse or invalid params error
- Payment not provided or insufficient USDC triggers a 402 Payment Required response
- Network congestion or node unavailability may cause timeouts
- Querying a contract address that doesn't exist on ApeChain returns null or zero values

## 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 the result of the requested blockchain method call — such as block data, account balance, transaction details, or smart contract return values — following the Ethereum JSON-RPC specification adapted for ApeChain.

## 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-apechain-rpc-endpoint-b61b8775/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)