For x402 vendors
Be verifiable without becoming public.
An identity-verified person answers for your payTo address and resource URL. The attestation travels in your 402 response, and nobody learns who stands behind it.
From your account to your first verdict.
- Create your account; the responsible person signs in with a passkey.
- Bind the wallet that controls your payTo address and register your endpoint.
- Verify the responsible person's identity on the provider's page.
- Acknowledge the terms with your wallet, then choose your tier and billing.
- Issue the attestation; your middleware attaches it to every 402 response.
- Read your first verdict, as any buyer does.
Anyone reads your verdict before paying.
Buyers, agents, explorers and marketplaces read the verdict on your endpoint: verified, not verified or unknown.
The protocol charges nothing to verify; operators price their own services.
Every integration keeps working when no verdict is available: the badge falls back to "unknown", and nothing in the buyer's, seller's or platform's flow ever waits on us.
Two tiers, by the volume you sell and who you answer to.
Attested Vendor
For sellers with real commercial volume.
Regulated / Compliance
For obliged entities, and the platforms that answer to a regulator.
For operators with meaningful volume — not for micro-transactions.