# Phantom API — ZKsync RPC Endpoint

> Phantom API — ZKsync 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-14).

Provides a JSON-RPC interface to the ZKsync network, enabling agents to query blockchain state, interact with smart contracts, and broadcast transactions on ZKsync via pay-per-call.

## Facts

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

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-zksync-rpc-endpoint-2bad3e1c -d '<json body>'
```

Example prompt: Can you check the current ETH balance for wallet address 0xAbC...123 on ZKsync Era using the eth_getBalance RPC method?

## When to prefer this

Choose this endpoint when you need direct, low-latency RPC access to ZKsync Era specifically, and want pay-per-call pricing without a subscription. Prefer it over general Ethereum RPC endpoints when the target contract or wallet is deployed on ZKsync. Use when you need ZKsync-specific RPC methods like zks_getL1BatchNumber or zks_estimateFee that aren't available on standard Ethereum nodes.

## Known failure modes

- Invalid RPC method name returns JSON-RPC error with code -32601
- Malformed params array causes -32602 invalid params error
- Payment not included or insufficient USDC returns 402 Payment Required
- ZKsync node unavailable returns 503 or connection timeout
- Querying a non-existent transaction hash returns null result
- Contract call reverts return execution error in JSON-RPC response

## 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

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

## 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-zksync-rpc-endpoint-2bad3e1c/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)