# Phantom API — Sonic Latest Block

> Phantom API — Sonic Latest Block 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).

Fetches the most recent block data from the Sonic blockchain network via pay-per-call on-chain infrastructure

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/sonic/block/latest
- 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-sonic-latest-block-5ebc65f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-nNM4viL7hcGGyZN8JeDO

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-sonic-latest-block-5ebc65f6 -d '<json body>'
```

Example prompt: What's the latest block on the Sonic blockchain right now — give me the block number, hash, and timestamp?

## When to prefer this

Choose this endpoint when you need real-time latest block data specifically from the Sonic blockchain and want a pay-per-call model without subscription overhead. Useful for agents that need on-demand chain state checks without maintaining a dedicated RPC node.

## Known failure modes

- Payment not included or insufficient USDC — returns 402 Payment Required
- Sonic network RPC node unavailable — may return 503 or timeout
- Malformed POST body (wrong bodyType or missing required fields) — returns 400 Bad Request
- Network congestion causing delayed or stale block data
- Vercel cold-start latency on first call

## 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 on-chain metadata for the most recently produced block on the Sonic network, including block number, block hash, parent hash, timestamp, transaction count, and other standard block header fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "properties": {},
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-sonic-latest-block-5ebc65f6/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)