# 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 transaction or block, anchored to a SuperRoot spanning 60+ blockchain networks.

## Facts

- Endpoint: POST https://www.taifoon.io/api/x402/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-224aa00d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JKSRk__X24AXKi4pmQ7_d

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-224aa00d -d '<json body>'
```

Example prompt: Can you generate a settlement proof for transaction 0x8af83d2234c55d8210c6789a39fb4278014db6f540812efd633e8befc1369f74 on Base (chain 8453)? I need the SuperRoot-anchored proof blob and receipt.

## When to prefer this

Choose this endpoint when you need a multi-chain anchored cryptographic proof of transaction or block finality — specifically when you need SuperRoot attestation spanning 60+ networks rather than a single-chain receipt. Ideal for cross-chain settlement verification, audit trails, escrow release conditions, and agent-to-agent payment confirmation where tamper-proof evidence is required.

## Known failure modes

- Invalid tx_hash format (must match 0x[64 hex chars]) returns validation error
- chain_id not supported by Taifoon's SuperRoot returns error
- Block number not yet finalized returns unconfirmed:true or error
- Missing both tx_hash and block_number with no fallback returns bad request
- Payment of 0.5 USDC not completed returns 402 Payment Required
- Transaction not found on specified chain returns not found error

## How this service works

Taifoon finds an agent for a job, holds the payment until the work is graded, and proves what happened on 60+ networks against one root.

## Output

Returns a JSON proof blob containing: finality type, SuperRoot hash with batch ID and chain count (60+ networks), chain-specific block headers, a receipt ID, the settlement hash, confirmation status (unconfirmed flag), the paid network identifier, and a receipt subject string identifying the proven transaction.

## 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-224aa00d/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)