# PayPerByte x402 Gateway – Liquidation Stream

> PayPerByte x402 Gateway – Liquidation Stream is a paid API for AI agents from x402.payperbyte.io, paid per call via x402, $0.03/call, status down (last checked 2026-09-15).

Returns a real-time feed of DeFi liquidation events with cryptographic EIP-712 attestation proving delivery and data authenticity.

## Facts

- Endpoint: POST https://x402.payperbyte.io/feeds/liquidation-stream
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payperbyte-x402-gateway-liquidation-stream-63967013
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2dCw8kcYtcKRSffjMQJWG

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 payperbyte-x402-gateway-liquidation-stream-63967013 -d '<json body>'
```

Example prompt: Pull the latest DeFi liquidation stream from PayPerByte — I need the current liquidation events with the EIP-712 attestation receipt so I can verify the data before acting on it.

## When to prefer this

Choose this endpoint when you need real-time DeFi liquidation event data with cryptographic proof of authenticity — specifically EIP-712 attestation at both the gateway and per-feed publisher level. Prefer it over unattested liquidation feeds when your agent must verify data provenance before acting (e.g. risk engines, trading bots, compliance workflows). The micropayment model ($0.03/call via x402) makes it suitable for on-demand polling without subscriptions. Use this over centralized liquidation APIs when tamper-evidence and on-chain anchoring are requirements.

## Known failure modes

- Missing or invalid x402 payment header — payment not processed, endpoint returns 402 Payment Required
- Insufficient USDC balance — payment fails, no data returned
- Feed temporarily unavailable — upstream liquidation data source offline
- Invalid request format — POST body malformed, returns 4xx error
- On-chain attestation txHash not yet confirmed — attestation verification may lag block time
- Rate limiting if payment flow is disrupted mid-request

## How this service works

Cryptographically attested, first-party data feeds for AI agents — covering crypto markets, DeFi yields, weather, earthquakes, news, code-pulse, threat-intel, address reputation, sanctions screening, and supply-chain verdicts. Every paid response carries EIP-712 receipts you verify before acting: (1) a GATEWAY delivery-integrity receipt (X-BYTE-Attestation header, signed by the PayPerByte gateway key) proving these are exactly the bytes we served; and (2) on the 14 attested feeds (provenance:eip712-attested in GET /feeds), a LIVE per-feed PayloadAttestation by that feed's OWN distinct publisher key, anchored ON-CHAIN — recover it from the broadcast the response references via txHash. (Separately, the POST verdict oracles embed their own per-feed `attestation` directly in the response body — recover attestation.signer.) Both attest authenticity + tamper-evidence under the BYTE Library domain. NEITHER asserts the correctness of the underlying data or any verdict, and NEITHER claims an independent third-party data source signed it — all keys are first-party PayPerByte. Pay per call in USDC over x402 with no API keys — a wallet, not a secret on the box. Settlement is on Base (eip155:8453). Price is per-feed, derived from expected payload size at $0.005000/KB (floor $0.001000).

## Output

A JSON response with the feed name ('liquidation-stream') and current liquidation event data. The response includes an X-BYTE-Attestation header (gateway delivery-integrity receipt signed by PayPerByte's gateway key) and, for attested feeds, a per-feed PayloadAttestation anchored on-chain via a txHash. The payload proves both that these exact bytes were served by PayPerByte and that the feed publisher signed the underlying data.

## 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",
     "required": [
      "asset"
     ],
     "properties": {
      "asset": {
       "type": "string",
       "pattern": "^[A-Za-z0-9]{1,10}$",
       "description": "Asset symbol (OKX USDT-SWAP underlying), e.g. BTC."
      },
      "window_h": {
       "type": "number",
       "maximum": 72,
       "minimum": 1,
       "description": "Lookback window in hours (default 6). Committed into the answer as window_start_ms/window_end_ms for /verify reproducibility."
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "feed": "liquidation-stream"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payperbyte-x402-gateway-liquidation-stream-63967013/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.payperbyte.io](https://www.zero.xyz/host/x402.payperbyte.io/llms.txt)