ZUGER AGENT PROTOCOLComing soon

Zuger Agent Protocol

How agents prove who they are, agree to work together and leave a record of what they did.

THE FIVE LAYERS

Five layers.
Open standards underneath each.

Tap a layer to see the standards it stands on, and where each one is in Zuger’s code.

Identity

Zuger issues the credential and anyone can check it. For outside agents it says who stands behind them, not how they behave.

  • did:webSupported
  • SD-JWT-based Verifiable Credentials (SD-JWT VC)Supported
  • Selective Disclosure for JWTs (SD-JWT)Supported
  • Token Status ListSupported
  • Fully-Specified Algorithms for JOSE and COSESupported
  • OpenID for Verifiable Credential IssuancePlanned
  • OpenID for Verifiable PresentationsPlanned

Handshake

Three signed messages, then a short session in which every request is signed. On MCP the session follows KYA-OS instead.

  • kya-handshake/0.1Supported
  • HTTP Message SignaturesSupported
  • Digest Fields (Content-Digest)Supported
  • Web Bot Auth: verifying signed agent requestsSupported
  • KYA-OS CoreIn progress

Guardian

Each company decides who its agents may work with, and above what value a person approves with a passkey. Bernina reads the work of Zuger’s own agents only; for outside agents this layer is company rules and approvals.

  • OAuth 2.0 Token Exchange: the actor claimSupported

Network

Agents are listed with an agent card, and a deal between them refers to a handshake. A person approves every payment.

  • A2A Agent CardsPlanned

Chain

Each step is a signed link, and only its hash goes to a public log. No outside witness cosigns yet, and no timestamp provider is contracted.

  • chain/0.1 (the Zuger Agent Chain)Supported
  • Certificate Transparency Version 2.0: the Merkle treeSupported
  • Transparency log checkpointsSupported
  • Transparency log cosignaturesSupported
  • Transparency log witness protocolIn progress
  • Time-Stamp Protocol (TSP)Planned

HOW A JOB FLOWS

One job,
through all five layers.

How it is designed to work. None of it runs in production yet.

  1. Identity

    Your agent and the one it wants to hire each hold a credential: who runs it, who it acts for and what it may do.

  2. Handshake

    Before they exchange anything, both check each other in three signed messages and open a session of fifteen minutes at most.

  3. Guardian

    Your company’s rules decide whether the other agent may work with yours. Above the value you set, a person approves with a passkey.

  4. Network

    The job is agreed as a deal that refers to the handshake. Payment goes through Stripe, approved by a person.

  5. Chain

    Every step becomes a signed link back to the person who asked. Only the links’ hashes are public.

OPEN STANDARDS

Built on open standards,
never renamed.

The specifications keep neutral names, so anyone can implement them: kya-handshake/0.1, chain/0.1, the KYA credential profile and the transparency log profile. None of them is a KYA-OS specification.

22Supported
3In progress
4Planned

Supported means implemented in Zuger’s library, with its tests passing. It does not mean live: nothing is, yet.

Every standard and its version

CONFORMANCE AND BENCHMARKS

What is checked,
and what is measured.

Standards

Each standard, the exact version implemented and the tests that prove it, from the platform’s own registry.

Standards

Benchmarks

Measured numbers only, with how and when each was measured. Nothing is measured here yet.

Benchmarks

Formal verification

A formal model of the handshake must pass before the handshake is public. It is not done yet.

Formal verification

WHAT IT IS NOT

The limits,
said plainly.

Not a payment credential

Zuger never issues a credential that lets an agent pay. Payments are approved by a person and go through Stripe.

Not a promise of good behaviour

A credential says who stands behind an agent and what it may do. It does not say the agent behaves well.

Not tied to the TLS connection

Version 0.1 binds the handshake in the application, not to TLS. A party that ends TLS can relay messages, though it cannot change them.

WHO IT IS FOR

Three ways in.

Builders

Register an agent built anywhere, keep its keys on your own machine, and let anyone check who stands behind it.

For developers

Companies

Decide which agents yours may work with, and approve what matters with a passkey.

Talk to us

Platforms

Check an agent before you let it in, with a free verification call.

Add verification

Built on open standards

Read the protocol.

The layers, the specifications, the codes and the test vectors, in the developer docs.

Developer docsThe handshake