Your first customer should not be your integration test.
For paid agents, “works on my machine” is dangerous.
The real product is the full path:
request → payment → settlement → delivery
Someone should test that before the first real buyer does.
PreFlight verifies PreFlight.
A real x402 buyer flow completed:
authorization → settlement → delivery → RELEASE → signed receipt
The receipt is publicly verifiable:
https://t.co/qEpxrud4XK
A paid agent doesn’t have one failure point.
REQUEST → 402 → PAYMENT → SETTLEMENT → DELIVERY
> The endpoint can be online while price is wrong.
> Payment can settle while delivery fails.
> The listing can differ from runtime.
PreFlight tests the transaction, not the ping.
PreFlight is now live on https://t.co/K61Ffl6eqs.
ASP #5161 is listed and ready to verify paid agent services before their first real buyer finds the failure.
200 OK is not ready to sell.
Test the transaction, not the ping.
Your paid agent can be live and still fail its first buyer.
PreFlight is the release gate: free discovery, then an authorized bounded buyer test across x402 payment, settlement, & delivery
RELEASE / BLOCK / UNKNOWN, with evidence & the exact fix.
https://t.co/s6rFtQRzGY
#OKXAI
PreFlight is submitted to https://t.co/K61Ffl6eqs as ASP #5161 and is currently under review.
The implementation is public for technical review:
https://t.co/6Y3yK8mdIR
Building a paid agent service? Send us a public endpoint or Agent ID. We’ll start with free discovery.
Your paid agent can be live and still fail its first buyer.
PreFlight is the release gate: free discovery, then an authorized bounded buyer test across x402 payment, settlement, & delivery
RELEASE / BLOCK / UNKNOWN, with evidence & the exact fix.
https://t.co/s6rFtQRzGY
#OKXAI
Every completed full verification can issue an Ed25519-signed receipt over the decision, manifest hash, runtime snapshot, and policy version.
Use the same release gate through the Web, API, hosted MCP, or npm CLI:
npm i -g @vinaystwt/preflight-cli