Integrations
One header to publish. One free check to read.
x402 is the first rail we cover. Nothing in it changes.
If you sell
A small middleware attaches the attestation header whenever your server answers 402. Payment logic unchanged. Calls to ZadQ use an API key or a short-lived session credential, issued to your company.
If you buy, or route for others
Client software verifies the issuer's signature on your own infrastructure, against published keys. Free, in under ten seconds. What you do with not verified or unknown is your policy.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.