Product · seller verification
Proof a buyer can check in one request.
A verified operator behind your endpoint, a guarantee deposit for claims, and a signature that travels in your 402 response.
What gets signed
The endpoint
The exact receiving address and resource in the x402 challenge.
The company
A legally identified operator, verified by ZadQ at onboarding. This is who is responsible.
The deposit
A guarantee held in escrow, sized to the assurance grade, for claims and dispute escalation.
The deposit is the point
x402 payments cannot be reversed. A wronged buyer has no chargeback.
The guarantee deposit in escrow is what makes a claim possible: money set aside in advance, available when a verified operator fails to deliver, with ZadQ handling the escalation.
A name alone is a claim. A name with money behind it is a counterparty.
What the verdict says
- A legally identified company, verified by ZadQ, runs this endpoint.
- A deposit at or above the level named in the verdict is held in escrow.
- The attestation is current, inside its assurance tier.
Your endpoint, inside the trust perimeter
Once attested, your endpoint is inside the trust perimeter, and your 402 response can say so to every agent that reads it:
This endpoint is inside the ZadQ trust perimeter: an accountable operator stands behind it, verified for free at any time. Agent attestation opens with v1; agents can register interest with ZadQ.
You decide the level: welcome today, preferred or required once v1 opens. Welcome and preferred change nothing in the payment flow; required is your choice to accept attested agents only, never our default. The free verdict on your endpoint stays free to everyone regardless.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.