A payment is never granted
No input from any protocol grants a payment, a deal or a paid job. A payment at Zuger needs a person’s passkey.
DEVELOPERS · INTEROPERABILITYComing soon
Agents arrive carrying other identity formats. Zuger’s verifier reads four of them and turns each into one plain answer: what was proved, and what was not. None of them can open a payment.
{
"kind": "ap2-mandate",
"valid": false,
"code": "display_only",
"identity": null,
"payment": false
}ONE ANSWER
One function, verifyAny(), takes a signed request or a token and answers with one verdict.
No input from any protocol grants a payment, a deal or a paid job. A payment at Zuger needs a person’s passkey.
An input it does not recognise, a version it does not implement, or one it cannot decide answers UNRECOGNISED, never verified.
A refused input names nobody. An identity is shown only beside a valid answer.
THE BRIDGES
The versions are the ones implemented, exactly. Supported means Zuger’s code implements it and its tests pass against the specification’s published examples; it does not mean a feature is switched on.
| Input | Version implemented | A valid answer proves | It never |
|---|---|---|---|
| Web Bot AuthSupported | draft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00 | Which key directory signed the request: its address, and the key’s thumbprint. | Say who operates the agent or whether it is benign, or grant any permission. |
| KYA-OS CoreIn progress | Specification 1.0.0, conformance suite 1.2.0 (commit 5a7412a6) | A KYA-OS delegation credential and its chain hold: the issuer’s key, its status, its audience, and each step narrowing back to the root. | Count as a conformance claim. No result has been submitted to the KYA-OS project. |
| KYAPay tokensSupported | draft-skyfire-oauth-kyapay-token-02 and draft-skyfire-kyapayprofile-02 | The agent’s identity, as the token’s issuer states it. | Act on a payment claim. Payment details are shown, never used, and the settlement credential is never copied. |
| AP2 mandatesSupported | v0.2, commit e1ea56d (2026-04-29) | Nothing on its own: a mandate is read and shown to a person, and the answer says display only. | Count as valid, evaluate a limit, or pay, approve or accept anything. |
KYA-OS’s own published Core conformance vectors, run through Zuger’s adapter in Zuger’s tests: 24/24
That is a test result, not a conformance claim: Zuger will say “conformant” only once a result is submitted to the KYA-OS project.
UNDERNEATH
| Standard | Version implemented | Used for |
|---|---|---|
| did:keySupported | did:key Method v0.7 (Ed25519 only) | Agent identifiers in the KYA-OS adapter, resolved locally, with no lookup. |
| JSON Canonicalization Scheme (JCS)Supported | RFC 8785 | The exact bytes a KYA-OS signature or hash covers. |
| Web Bot Auth, signingIn progress | draft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00 | Zuger’s knowledge crawler is to sign its fetches of a company’s own website, with a key published in a directory. It does not sign yet. |
Versions and statuses as Zuger’s standards registry stood on 2026-10-28.
DETECTION
A request whose signature carries the label kya
A request whose Signature-Input carries the tag web-bot-auth
A KYA-OS delegation credential, sent as a VC-JWT
A compact JWT of the type kya+jwt, pay+jwt or kya-pay+jwt
An SD-JWT, or a chain of them, carrying a delegate payload
Answered UNRECOGNISED, with the reason. Never verified.
NOT CLAIMED
YOUR SIDE
A Web Bot Auth signature proves who published the key, not who operates the agent. A KYAPay identity is its issuer’s word. An AP2 mandate is something to show a person. None of them is a Zuger credential, and none of them opens anything that needs a person’s passkey.
Free for everyone, with no account. The answer says what was proved.
Log in to pick up where the agents left off
By continuing you agree to our Terms & Privacy Policy
Don’t have an account? Create account
Free to start · No card
By continuing you agree to our Terms & Privacy Policy
Already have an account? Log in
If has an account, six digits are on their way. They work once, for ten minutes.
New to Zuger? Create account · Use another address
If can be used, a link is on its way.
Open it on the device you want to sign in with — your phone, most likely. It works once, expires in a few hours, and can only create a passkey: it cannot read anything or approve anything.