Credential profiles
Both profiles’ credentials, the outside-agent identifier, a status list, verification cases and issuance refusals.
Coming soonBuilt on open standards. The five layers, the open specifications underneath, what passes its tests, the test vectors and what changed.
THE FIVE LAYERS
| Layer | What it does | Status |
|---|---|---|
| 01 Identity | A 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 Handshake | Both 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 Guardian | Company 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 Network | A 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 Chain | Every 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
Drafts today. They will be published with the reference library under the Apache 2.0 licence; until then this page says what each covers.
| Specification | Identifier | What it covers | Status |
|---|---|---|---|
| KYA credential profile | kya/agent/v0.1 · kya/ext-agent/v0.1 | The 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.1 | kya-handshake/0.1 | Two agents prove themselves to each other in three messages and agree a session, over HTTPS and A2A. Read it. | Draft |
| chain/0.1 | chain/0.1 | Signed steps from a person’s decision to what the agents did for them. | Draft |
| Transparency log profile | kya-log | A public, append-only log of credential and link hashes, with signed checkpoints. | Draft |
CONFORMANCE
From the platform’s standards registry, built into this page. A row says Supported only when the tests it names pass.
| Checked against | Standards |
|---|---|
| The specification’s own published examples | 15 |
| Another implementation’s published test data | 3 |
| Zuger’s own tests | 7 |
KYA-OS: In progress. A conformance level is claimed only once a result has been submitted.
TEST VECTORS
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.
Both profiles’ credentials, the outside-agent identifier, a status list, verification cases and issuance refusals.
Coming soonA case for every result code, the approval flow on both sides, and reflection, replay, downgrade and one-sided cases.
Coming soonA case for every chain result code.
Coming soonThe files will be published with the specifications. Today they run in Zuger’s own tests.
CHANGELOG
| Date | Change |
|---|---|
| 2026-10-28 | The standards registry and the benchmark figures: every standard with the version implemented, every figure with how it will be measured. |
| 2026-10-27 | The 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-27 | Keys an owner approves with a passkey, for outside agents: 24 hours at most. Switched off. |
| 2026-10-25 | Registration 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-24 | kya-handshake/0.1 and chain/0.1 drafted and built as a library, with a test vector for every result code. |
| 2026-10-24 | The KYA credential profile, version 0.1, for Zuger’s agents and for outside agents, with its verifier, built as a library. |
Registration opens with the developer portal. The docs say how it will work.
For developersFormal verificationLog 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.