# Phantom API – Katana Latest Block

> Phantom API – Katana 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 Katana network via Phantom's Web3 infrastructure

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/katana/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-katana-latest-block-78c94cfb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2zsGS2ag4Lju2z3ZHd2cT

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-katana-latest-block-78c94cfb -d '<json body>'
```

Example prompt: What's the latest block on the Katana network? Pull the current block number, hash, and timestamp right now.

## When to prefer this

Use this endpoint when you need fast, pay-per-call access to the latest Katana block without managing your own RPC node infrastructure. Prefer it over self-hosted nodes for lightweight agents that need occasional real-time block data without the overhead of maintaining a node subscription.

## Known failure modes

- Network timeout if Katana RPC node is unreachable
- Empty or malformed block response if the node is syncing
- HTTP 402 Payment Required if USDC payment via x402 is not included or fails
- HTTP 500 if Phantom's backend infrastructure is unavailable
- Stale block returned if the underlying node is behind the chain tip

## 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 the latest block object from the Katana network, typically including block number (height), block hash, parent hash, timestamp, and a list of included transactions or transaction hashes.

## 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-katana-latest-block-78c94cfb/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)