For businesses that accept agents
No identity checks to run, no identity documents to keep.
The person behind each bounded agent verified once, with the issuer. Your service checks the agent on every request and never learns who that person is.
Your service checks agents. The identity work is already done.
No identity verification of your own
Accept agents that an identity-verified person answers for, without an identity check of your own: the person verified once, with the issuer, so your service runs no identity verification and stores no identity document for them.
Paid for each person you send to verify once
When your service turns away an agent nobody answers for, the refusal can send that agent's person to verify once with ZadQ. For each person who arrives that way and keeps a paid plan, ZadQ pays your business a referral share.
Counted once per person, on a plan that is paid and not refunded, as a credit on your invoice or a monthly payout.
If the law obliges your business to identify its customers, those duties stay yours; nothing here changes them.
Your service learns what it asked for, never who.
It learns
- The conditions your policy asks for, checked on every request: the grade, the scope, the limit and the expiry.
- A pseudonym per agent that keys your ledger and means nothing at any other service.
It never learns
- The person's name or documents.
- Which other agents that person runs, or where they go.
A presentation proves those conditions against the chain it is bound to; it does not tell you how recently the person was verified.
Connect an agent once, then check it on every request.
- Your customer chooses Connect an agent on your service.
- Your verifier sends a ten-second challenge that carries your policy.
- On accept, you store the pseudonym, a name, a limit and an approval rule.
- Every later request carries a fresh presentation; you apply your ledger and your limit.
- A switched-off agent fails its next check with a closed reason.
Where accountable agents earn better terms.
Paid APIs and metered data
Open a quota, credit or a closed route to agents a person answers for.
You already price access. An anonymous script gets your public terms; an agent someone answers for can get more.
On paid routes the check travels in the 402 response you already send, and the agent's pseudonym keys its quota.
Status: The x402 identity leg is in production.
Developer and orchestration platforms
Let your users' agents through other sites' doors.
Each of your users verifies once with ZadQ, and every agent they run carries a bounded mandate any site can check.
You run no identity checks, and your users' names never reach the sites.
Status: The refusal that sends a person to verify is being built.
Reference and community content
Give a person's assistant a person's pace.
A pseudonym per agent lets you rate-limit each one, and you learn nothing about the person.
Status: For ordinary routes, the OAuth bridge is a draft.
Start in your account.
- Your responsible person creates the account with a passkey and verifies their identity once.
- You open the verifier product and run the verifier kit, included in your account. It generates your request key on your machine, and the key never leaves it.
- ZadQ files your admission request to production under the network's published admission policy; your dashboard shows the turnaround.
Or let ZadQ run your verifier under your origin, as a managed deployment. Being prepared.
The protocol charges nothing to verify; operators price their own services.