# Phantom API — MegaETH RPC Endpoint

> Phantom API — MegaETH 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-15).

Executes JSON-RPC calls against the MegaETH blockchain network, enabling on-chain data queries and smart contract interactions via pay-per-call x402 payments.

## Facts

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

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-megaeth-rpc-endpoint-0cce778b -d '<json body>'
```

Example prompt: What's the current block number on MegaETH? Use eth_blockNumber to fetch it.

## When to prefer this

Choose this endpoint when you specifically need to interact with the MegaETH network via standard EVM JSON-RPC methods. It is well-suited for pay-per-call agent workflows where you want to avoid managing node infrastructure, and when you need real-time on-chain data from MegaETH specifically rather than Ethereum mainnet or other EVM chains.

## Known failure modes

- Invalid JSON-RPC method name returns an error response
- Malformed params array causes a parse error
- Payment failure via x402 returns 402 Payment Required before the RPC call is made
- Network unavailability returns a 503 or timeout
- Unsupported method for MegaETH returns method not found error

## 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 field with the requested on-chain data (e.g. block number, balance in wei, transaction receipt, contract return value) or an error object if the call failed.

## 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-megaeth-rpc-endpoint-0cce778b/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)