Skip to content
PreFlight
Controlled exampleOne preconfigured service, one known mismatch

Watch a release get blocked, then fixed, then released.

This runs the same instrument you get on a real report. The failure is deliberate: an all green demo proves nothing. The block proves PreFlight catches a real consequence.

PREFLIGHT LIVE CHECKX LAYER · 00:05.342
okx://agent/quote-svc · https://api.quote.example/mcpLIVE
TARGETokx://agent/quote-svc
DECLAREDpayTo 0x71A8…45E2
OBSERVEDpayTo 0x442B…9C07
EXACT FIX · PAY-04

Point the endpoint payTo to your declared address, then rerun.

SIGNED RECEIPTBILL_OF_LADING · pfr_01KXBP…051PN · Ed25519SIGNATURE VALIDsha256:f1afc114…2bde0fc8
VERDICTBLOCKRELEASE
EXECUTION
  1. LISTING
  2. DISCOVERY
  3. REQUEST
  4. 402
  5. PAYMENT
  6. SETTLEMENT
  7. DELIVERY
  8. VERDICT

Demo pacing. Click to replay.

The story, one beat at a time.

  1. 01

    Intended

    The operator declares a release for quote-svc: price 0.10 USDT, paid to their own wallet, a required token input.

  2. 02

    Observed

    PreFlight becomes a buyer. Discovery, the 402, payment, settlement, and delivery all pass.

  3. 03

    Block

    One criterion contradicts: the live payTo is a different address than declared. Funds would leave to the wrong wallet, so the release is blocked.

  4. 04

    Fix

    The operator fixes the deployment, not the manifest. The endpoint payTo now matches what was declared.

  5. 05

    Release

    The same manifest is rerun. Every mandatory criterion matches the new snapshot. The release is sellable.

Every value here maps to a real report.

Run a check on your own service to get the private report and the exact fix.

Run a check