DEVELOPERS · PROTOCOLComing soon

Zuger Agent Protocol (ZAP)

Built on open standards. The five layers, the open specifications underneath, what passes its tests, the test vectors and what changed.

THE FIVE LAYERS

What each layer does.

LayerWhat it doesStatus
01 IdentityA credential for every agent: who stands behind it, who it acts for and what it may do.Zuger issues the credential and anyone can check it. For outside agents it says who stands behind them, not how they behave.Coming soon
02 HandshakeBoth agents prove who they are before they work together.Three signed messages, then a short session in which every request is signed. On MCP the session follows KYA-OS instead.Coming soon
03 GuardianCompany rules and a person’s approval, for every agent.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.Coming soon
04 NetworkA directory to be found in, signed deals and receipts, and reputation.Agents are listed with an agent card, and a deal between them refers to a handshake. A person approves every payment.Coming soon
05 ChainEvery action chained back to the person who asked; witnessed and timestamped.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.Coming soon

OPEN SPECIFICATIONS

The specifications,
with neutral names.

Drafts today. They will be published with the reference library under the Apache 2.0 licence; until then this page says what each covers.

SpecificationIdentifierWhat it coversStatus
KYA credential profilekya/agent/v0.1 · kya/ext-agent/v0.1The agent’s credential: an SD-JWT VC with its key, its operator, what it may do and how to check it is not revoked.Draft
kya-handshake/0.1kya-handshake/0.1Two agents prove themselves to each other in three messages and agree a session, over HTTPS and A2A. Read it.Draft
chain/0.1chain/0.1Signed steps from a person’s decision to what the agents did for them.Draft
Transparency log profilekya-logA public, append-only log of credential and link hashes, with signed checkpoints.Draft

CONFORMANCE

What passes its tests.

From the platform’s standards registry, built into this page. A row says Supported only when the tests it names pass.

22Supported
3In progress
4Planned
Checked againstStandards
The specification’s own published examples15
Another implementation’s published test data3
Zuger’s own tests7

KYA-OS: In progress. A conformance level is claimed only once a result has been submitted.

Every standard and its version

TEST VECTORS

Test vectors,
byte for byte.

Each set is made by a generator and checked byte for byte in the platform’s tests. Keys come from fixed labels and clocks are fixed: the keys are test keys and public.

Credential profiles

Both profiles’ credentials, the outside-agent identifier, a status list, verification cases and issuance refusals.

Coming soon

kya-handshake/0.1

A case for every result code, the approval flow on both sides, and reflection, replay, downgrade and one-sided cases.

Coming soon

chain/0.1

A case for every chain result code.

Coming soon

The files will be published with the specifications. Today they run in Zuger’s own tests.

CHANGELOG

What changed.

DateChange
2026-10-28The standards registry and the benchmark figures: every standard with the version implemented, every figure with how it will be measured.
2026-10-27The Zuger Agent Chain and the transparency log as services, switched off. The KYA-OS adapter. One verifier for other formats: Web Bot Auth, KYAPay for identity, AP2 mandates for display.
2026-10-27Keys an owner approves with a passkey, for outside agents: 24 hours at most. Switched off.
2026-10-25Registration of outside agents, and hardening: an algorithm allow list, cheap checks before any cryptography, proof of work under load, freezing an agent. Switched off.
2026-10-24kya-handshake/0.1 and chain/0.1 drafted and built as a library, with a test vector for every result code.
2026-10-24The KYA credential profile, version 0.1, for Zuger’s agents and for outside agents, with its verifier, built as a library.
Built on open standards

Register an agent.

Registration opens with the developer portal. The docs say how it will work.

For developersFormal verification