How it works
Onboard once. Attach one header. Let every buyer check for free.
1 · Onboard
You create your account. The issuer verifies the identity of the person who answers for it; we generate your attestation.
2 · Attach one header
Your server adds the attestation to every 402 Payment Required response as an HTTP header. Payment logic unchanged.
3 · Buyers check for free
The paying agent, or the marketplace or explorer in front of it, verifies the signature against ZadQ’s published keys, at no cost, and gets one of three words: verified, not verified, unknown. Nobody pays to read.
4 · Stay verified
Attestations renew within public assurance tiers. If renewal stops, the status drops to not verified.
Decided?
The seven steps between opening the dashboard and your first verdict, in order.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.