ZUGER KYA · KNOW YOUR AGENT

Know your agent.

Every agent gets a verifiable identity: who operates it, who it acts for and what it may do. Anyone will be able to check it, free, without an account.

Built, and not live yet

Nothing on this page is live yet. No credential has been issued, the public verifier is not open and the log is not published. This page describes what is built and how it will work; each part goes live on its own, and this list will say so.

  • Credentials for Zuger’s own agentsComing soon
  • Public verifier, freeComing soon
  • Live verification linksComing soon
  • Registration for agents built anywhereComing soon
  • Transparency logComing soon
  • Independent witnessesComing soon
  • Zuger Agent ChainComing soon
  • Emergency stopComing soon
  • Embeddable badgeComing soon

WHAT IT PROVES

Who runs it, who it works for, what it may do.

A Zuger credential is a short signed statement an agent carries and proves with its own key. It says who operates the agent, who it acts for when that company chooses to say so, what it may do, and until when.

Who operates it

Zuger Technologies OÜ for Zuger’s own agents. For an agent built anywhere, the company or the domain that registered it.

Who it acts for

The company it works for, shown only if that company chooses to disclose it.

What it may do

A short list of scopes, said in plain words. Anything not listed is refused.

How it was delegated

The approval a person gave with a passkey, and when.

Until when

A Zuger agent’s credential lives one Run, at most one hour.

Its key

The agent signs every request with a key the credential names. A copied credential is useless without it.

Part of the Zuger Agent Protocol (ZAP). Built on open standards.

HOW VERIFICATION LOOKS

A badge is drawn by whoever checks, never sent by the agent.

People will see the result of a live check, and agents will read it. The same five states wherever they are shown: the Console, the iPhone app, the verify page and any app with the SDK.

  • Verified by Zuger

    A valid credential, not revoked, and the business behind the agent passed Zuger’s check.

  • Zuger agent

    One of Zuger’s own agents. Zuger operates it and vouches for it, one Run at a time.

  • Registered

    An agent built anywhere. Its operator is known; it has not been vetted.

  • Unverified agent

    No credential, or one from an issuer the checker does not trust.

  • Revoked

    Expired, revoked, or signed with the wrong key. Never shown as anything softer.

The details sheet

Tap the result: the agent’s name, its operator and jurisdiction, who it acts for if disclosed, what it may do in plain words, the assurance, when it expires, its reputation, and Report this agent.

Only trust a live check

Agents never put a badge in a message, and Bernina refuses words that imitate one. Only trust a badge inside an app that checks it, or on zuger.ai. A picture of a badge proves nothing.

The live link

A Zuger agent’s message will carry a short link to zuger.ai/kya/v/…, which checks again every time it opens. No state in the link, no screenshot.

Agents can’t verify themselves

An agent can check another agent before it works with it. It can never check or vouch for itself, and no agent can register itself.

The mark and its rules

THE FULL PROCESS

Eight steps, from a business check to a key that is gone.

  1. 01

    KYB and hire

    A company passes the business check and hires an agent.

    KYB passed
  2. 02

    Issue

    A Run starts, and Zuger issues a credential for that Run alone.

    Valid for 1 hour
  3. 03

    Publish

    Zuger’s public keys are where anyone can read them.

    did:web:zuger.ai
  4. 04

    Approve

    A person approves the step that needs a person.

    Passkey approved
  5. 05

    Sign and send

    Bernina signs the request the agent sends.

    RFC 9421 signed
  6. 06

    Verify

    Whoever receives it checks the credential and the signature.

    Free check
  7. 07

    Decide

    Their own rules allow it or refuse it, and the decision is logged.

    Allowed · logged
  8. 08

    Expire

    The Run ends, the credential expires and the key is gone.

    Key destroyed

WHO DOES WHAT

Five parties, and each one’s part.

WhoTheir part
The customerPasses the business check, hires the agent, and approves with a passkey what needs a person.
ZugerIssues the credential for each Run, publishes its keys and the status list, and revokes.
BerninaInspects every Run of a Zuger agent and signs what it sends. Bernina never sees agents built elsewhere.
The agentProves its key on every request. It never holds a write credential and never signs outside its Run.
The counterpartyChecks, for free, and decides by its own rules whether to go on.

VERIFICATION

Six checks, in this order.

Every checker, the free API included, runs them in the same order and answers with the first one that fails.

  1. 1

    A credential and a signature

    The request carries both.

    missing_signature · missing_credential
  2. 2

    Resolve the issuer

    The issuer is on the checker’s trust list, and its signature holds.

    untrusted_issuer · bad_issuer_signature
  3. 3

    Check the credential

    Not expired, and not revoked in the status list.

    expired · revoked
  4. 4

    Match the key

    The request was signed by the key the credential names, and not sent before.

    key_mismatch · replay
  5. 5

    Evaluate the policy

    The checker’s own rules allow what the agent asks to do.

    out_of_scope
  6. 6

    Allow, and log it

    Every decision is logged with its reasons.

    ok

Per-Run credentials

Issued when a Run starts and gone when it ends, at most one hour later. The agent’s key is made inside the Run and never leaves it.

Bernina signs

Every request a Zuger agent sends is signed with HTTP Message Signatures (RFC 9421), inside an inspected Run.

Revocation

A revoked credential is flipped in a public status list. Checkers keep it for at most five minutes, and at most 60 seconds for sensitive scopes.

WHO CAN VERIFY, WHO CAN BE VERIFIED

Anyone can check. Any agent can be registered.

Anyone can check, free

People, platforms and other agents. No account needed.

Coming soon

Any agent, built anywhere

Registered free, or verified by Zuger after a business check.

Coming soon

Never itself

Agents never verify or vouch for themselves.

AGENTS BUILT ANYWHERE

Any agent, built anywhere, can be registered free or verified by Zuger.

For outside agents we vouch for who stands behind them, not for how they behave.

TierWhoThe checkPriceShown as
RegisteredAny developer or companyProof that you hold the domain, or a verified emailFreeRegistered
VerifiedAny companyA business check through StripeA yearly fee in euros, not set yetVerified by Zuger
Zuger agentZuger’s own agentsZuger operates themIncluded in every planZuger agent
  1. 01

    Sign up

    A person makes a developer account with a passkey. An agent never signs itself up.

  2. 02

    Register

    Name the agent, give its public key and say what it does. The private key stays with you.

  3. 03

    Get a credential

    Valid for 30 days, renewed while your account and your domain proof hold.

  4. 04

    Be verified

    Pass the business check, and the same agent keeps its identity at the higher tier.

An outside agent’s scopes are declared by its operator. Zuger does not run it, so it cannot enforce them, and the result says so.

WHERE TO CHECK

Six places to check an agent.

Every one of them runs a fresh check. None of them is live yet.

zuger.ai/verify

Paste, scan or drop what the agent gave you.

Coming soon

The live link

Every message from a Zuger agent will carry one. Tap it.

Coming soon

Inside Zuger

The Console, the iPhone app and every approval will show the result on their own.

Coming soon

In any app with the SDK

A platform draws the result after its own live check, like a browser padlock.

Coming soon

For agents

kya_verify over MCP, or the free API.

Coming soon

On other sites

The embeddable live badge.

Coming soon

CAN KYA BE HACKED?

Any single break is small, visible and reversible.

If someoneWhat stops it
Steals Zuger’s signing keyNo credential is issued yet, so there is no signing key to steal today. Where the keys live will be stated when KYA opens.
Takes over the zuger.ai domainA registry lock, DNSSEC and CAA on zuger.ai, an alert on any change to Zuger’s published keys, and no agent can touch those records.
Steals an agent’s keyIt lives one Run, at most an hour, in memory only.
Replays a signed requestEach signature covers the method, the address, the body, a 60-second window and a one-time nonce.
Fakes a businessNo Verified credential before the business check passes. Reputation starts at zero.
Talks an agent into moreA credential never widens what an agent may do. Bernina and your passkey gates stay as they are.
Counts on slow revocationCheckers keep the status list for five minutes at most, 60 seconds for sensitive scopes.
Floods the free checkerLimits per address and per agent before any cryptography, and it cannot be used to list anyone.

It proves identity, not good behaviour

A valid credential says who stands behind an agent. It does not say the agent’s work is right.

It is not permission to pay

Zuger never issues a payment capability. Payments come from regulated payment issuers.

It is not a certification

Zuger holds no certification for KYA and belongs to no standards body.

A public record, and a chain of responsibility.

Every credential Zuger issues or revokes goes into a public, append-only log, and every step an agent takes can be chained back to the person who asked.

Free plan · No card

Is this agent real?

Paste what an agent gave you and see who stands behind it. The public verifier is coming.