# Taifoon Settlement Proof

> Taifoon Settlement Proof is a paid API for AI agents from www.taifoon.io, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-16).

Generates a cryptographic settlement proof for a blockchain transaction or block, anchored under the SuperRoot across multiple chains

## Facts

- Endpoint: POST https://www.taifoon.io/api/skills/settlement-proof?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/taifoon-settlement-proof-24895efe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FgWxr5BTLHL2Wv13qRF-J

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 taifoon-settlement-proof-24895efe -d '<json body>'
```

Example prompt: Can you get me a settlement proof for transaction 0x381b311efe17fdce7e3e26d211253197bfb715195152b016b9576b6528989684 on Base chain (chain ID 8453)?

## When to prefer this

Use this endpoint when you need a cryptographic, SuperRoot-anchored proof of transaction or block finality on a supported EVM chain (especially Base chain 8453). It is ideal for compliance audits, escrow release triggers, cross-chain verification, and any workflow where you must demonstrate to a third party that a specific on-chain event is settled. Prefer it over block explorers when a machine-verifiable proof blob is required rather than a human-readable status page.

## Known failure modes

- Invalid or malformed tx_hash (must be 0x-prefixed 64 hex chars) returns a validation error
- Unsupported chain_id returns an error indicating the chain is not indexed
- Transaction not yet finalized may return unconfirmed: true or an error
- Neither tx_hash nor block_number provided may cause a missing-parameter error
- Payment failure (insufficient USDC) blocks the request before processing

## How this service works

Settlement Proof — chain_id=8453/tx_hash=0x381b311efe17fdce7e3e26d211253197bfb715195152b016b9576b6528989684

## Output

Returns a JSON proof blob containing the finality type, superroot metadata (batchId, chainCount, superrootHash), chain header details (chainId, blockHash, blockNumber), a receipt ID, settlement hash, unconfirmed flag, paid network identifier, and a receipt subject string identifying the proven transaction or block.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx_hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "the transaction whose block is proven"
  },
  "chain_id": {
   "type": "integer",
   "description": "chain id (8453 Base, 5042 Arc, 1 Ethereum, …)"
  },
  "block_number": {
   "type": "integer",
   "description": "or: the block to prove"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "skill": "settlement-proof",
  "proof_blob": {
   "finality": {
    "finalityType": 12
   },
   "superroot": {
    "batchId": 1790440016,
    "chainCount": 61,
    "superrootHash": "0x…"
   },
   "chainHeaders": [
    {
     "chainId": 8453,
     "blockHash": "0x…",
     "blockNumber": 51741672
    }
   ]
  },
  "receipt_id": "f0e1d2c3b4a5968778695a4b3c2d1e0f",
  "settlement": "0x…",
  "unconfirmed": false,
  "paid_network": "eip155:8453",
  "receipt_subject": "chain_id=8453/tx_hash=0x8af83d2234c55d8210c6789a39fb4278014db6f540812efd633e8befc1369f74"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/taifoon-settlement-proof-24895efe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.taifoon.io](https://www.zero.xyz/host/www.taifoon.io/llms.txt)