DEVELOPERS · INTEROPERABILITYComing soon

Other agent standards,
read honestly.

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

Whatever comes in,
three rules hold.

One function, verifyAny(), takes a signed request or a token and answers with one verdict.

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.

Nothing unknown is valid

An input it does not recognise, a version it does not implement, or one it cannot decide answers UNRECOGNISED, never verified.

A name only when valid

A refused input names nobody. An identity is shown only beside a valid answer.

THE BRIDGES

What each one proves,
and what it never does.

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.

InputVersion implementedA valid answer provesIt never
Web Bot AuthSupporteddraft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00Which 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 progressSpecification 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 tokensSupporteddraft-skyfire-oauth-kyapay-token-02 and draft-skyfire-kyapayprofile-02The 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 mandatesSupportedv0.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

The building blocks.

StandardVersion implementedUsed for
did:keySupporteddid:key Method v0.7 (Ed25519 only)Agent identifiers in the KYA-OS adapter, resolved locally, with no lookup.
JSON Canonicalization Scheme (JCS)SupportedRFC 8785The exact bytes a KYA-OS signature or hash covers.
Web Bot Auth, signingIn progressdraft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00Zuger’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

How an input is recognised,
in this order.

  1. 01

    Zuger’s own credential

    A request whose signature carries the label kya

  2. 02

    Web Bot Auth

    A request whose Signature-Input carries the tag web-bot-auth

  3. 03

    KYA-OS

    A KYA-OS delegation credential, sent as a VC-JWT

  4. 04

    KYAPay

    A compact JWT of the type kya+jwt, pay+jwt or kya-pay+jwt

  5. 05

    AP2

    An SD-JWT, or a chain of them, carrying a delegate payload

  6. 06

    Anything else

    Answered UNRECOGNISED, with the reason. Never verified.

NOT CLAIMED

What this page does not say.

  • Visa’s Trusted Agent Protocol: not claimed until Visa’s own documentation confirms it is Web Bot Auth.
  • ERC-8004: deferred until a customer asks for it. A lookup would need a new subprocessor.
  • KYA-OS conformance: not claimed until a result is submitted.
  • Membership of a standards body, a certification or a partnership: none is held, and none is claimed.

YOUR SIDE

What a verified identity is worth
is still your decision.

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.

Is the verifier answering? The status page

Free plan · No card

Check an agent,
whatever it carries.

Free for everyone, with no account. The answer says what was proved.