x402 Compliance Preflight
x402 revives the long-dormant HTTP 402 (Payment Required): a server answers 402, the agent pays on the spot in stablecoins, and gets a 200 with the content — one request, no account, no human in the loop. It lets machines pay per-call, per-unit, micro-value for APIs and content.
But paying fast is not paying compliantly. When the payer is code, who is paying, how far the mandate goes, and whether the counterparty is clean must all be decided before the money leaves — at machine speed. OceanAlt doesn't compete with x402; it acts as its companion, inserting a per-gate compliance check before settlement.
Our role: the compliance provider for x402
A companion, not a replacement
We don't rewrite x402 or compete with its facilitator for settlement. We sit one hop before settlement, rule on the payment intent, then hand off to x402 to finish 402 → 200.
Per-gate compliance check
An x402 payment first clears our gates: attribution (KYA), mandate & limits, a payment firewall, and counterparty AML screening. Pass and it settles; fail and it's stopped with a per-gate reason.
One line, protocol-neutral
Call /api/pay for a preflight before you initiate the x402 payment. No change to the x402 message, we don't custody your funds or consume a nonce. Also adapts to AP2 and other rails.
Verifiable, not a black box
Every decision ships per-gate checks and evidence you can click through to verify; the method maps to the openly published RAP framework.
Try it in your browser
Enter a payee address (0x / T / base58), plus optional amount and purpose, to preflight an x402 payment and see whether it clears — with a reason per gate. Stateless: no nonce consumed, no settlement, no credential required.
How to wire it in
Before your agent initiates the x402 payment, run a preflight on the same intent; continue to settlement on allow, abort on block. Integration code, mandate configuration and the self-describing gate list all live in the compliance-gateway console.