Who operates it
Zuger Technologies OÜ for Zuger’s own agents. For an agent built anywhere, the company or the domain that registered it.
ZUGER KYA · 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.
WHAT IT PROVES
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.
Zuger Technologies OÜ for Zuger’s own agents. For an agent built anywhere, the company or the domain that registered it.
The company it works for, shown only if that company chooses to disclose it.
A short list of scopes, said in plain words. Anything not listed is refused.
The approval a person gave with a passkey, and when.
A Zuger agent’s credential lives one Run, at most one hour.
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
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.
A valid credential, not revoked, and the business behind the agent passed Zuger’s check.
One of Zuger’s own agents. Zuger operates it and vouches for it, one Run at a time.
An agent built anywhere. Its operator is known; it has not been vetted.
No credential, or one from an issuer the checker does not trust.
Expired, revoked, or signed with the wrong key. Never shown as anything softer.
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.
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.
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.
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 FULL PROCESS
A company passes the business check and hires an agent.
KYB passedA Run starts, and Zuger issues a credential for that Run alone.
Valid for 1 hourZuger’s public keys are where anyone can read them.
did:web:zuger.aiA person approves the step that needs a person.
Passkey approvedBernina signs the request the agent sends.
RFC 9421 signedWhoever receives it checks the credential and the signature.
Free checkTheir own rules allow it or refuse it, and the decision is logged.
Allowed · loggedThe Run ends, the credential expires and the key is gone.
Key destroyedWHO DOES WHAT
| Who | Their part |
|---|---|
| The customer | Passes the business check, hires the agent, and approves with a passkey what needs a person. |
| Zuger | Issues the credential for each Run, publishes its keys and the status list, and revokes. |
| Bernina | Inspects every Run of a Zuger agent and signs what it sends. Bernina never sees agents built elsewhere. |
| The agent | Proves its key on every request. It never holds a write credential and never signs outside its Run. |
| The counterparty | Checks, for free, and decides by its own rules whether to go on. |
VERIFICATION
Every checker, the free API included, runs them in the same order and answers with the first one that fails.
The request carries both.
missing_signature · missing_credentialThe issuer is on the checker’s trust list, and its signature holds.
untrusted_issuer · bad_issuer_signatureNot expired, and not revoked in the status list.
expired · revokedThe request was signed by the key the credential names, and not sent before.
key_mismatch · replayThe checker’s own rules allow what the agent asks to do.
out_of_scopeEvery decision is logged with its reasons.
okIssued 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.
Every request a Zuger agent sends is signed with HTTP Message Signatures (RFC 9421), inside an inspected Run.
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
People, platforms and other agents. No account needed.
Coming soonRegistered free, or verified by Zuger after a business check.
Coming soonAgents never verify or vouch for themselves.
AGENTS BUILT ANYWHERE
For outside agents we vouch for who stands behind them, not for how they behave.
| Tier | Who | The check | Price | Shown as |
|---|---|---|---|---|
| Registered | Any developer or company | Proof that you hold the domain, or a verified email | Free | Registered |
| Verified | Any company | A business check through Stripe | A yearly fee in euros, not set yet | Verified by Zuger |
| Zuger agent | Zuger’s own agents | Zuger operates them | Included in every plan | Zuger agent |
A person makes a developer account with a passkey. An agent never signs itself up.
Name the agent, give its public key and say what it does. The private key stays with you.
Valid for 30 days, renewed while your account and your domain proof hold.
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
Every one of them runs a fresh check. None of them is live yet.
Paste, scan or drop what the agent gave you.
Coming soonEvery message from a Zuger agent will carry one. Tap it.
Coming soonThe Console, the iPhone app and every approval will show the result on their own.
Coming soonA platform draws the result after its own live check, like a browser padlock.
Coming soonkya_verify over MCP, or the free API.
Coming soonThe embeddable live badge.
Coming soonCAN KYA BE HACKED?
| If someone | What stops it |
|---|---|
| Steals Zuger’s signing key | No 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 domain | A 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 key | It lives one Run, at most an hour, in memory only. |
| Replays a signed request | Each signature covers the method, the address, the body, a 60-second window and a one-time nonce. |
| Fakes a business | No Verified credential before the business check passes. Reputation starts at zero. |
| Talks an agent into more | A credential never widens what an agent may do. Bernina and your passkey gates stay as they are. |
| Counts on slow revocation | Checkers keep the status list for five minutes at most, 60 seconds for sensitive scopes. |
| Floods the free checker | Limits per address and per agent before any cryptography, and it cannot be used to list anyone. |
A valid credential says who stands behind an agent. It does not say the agent’s work is right.
Zuger never issues a payment capability. Payments come from regulated payment issuers.
Zuger holds no certification for KYA and belongs to no standards body.
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.
Paste what an agent gave you and see who stands behind it. The public verifier is coming.
Log 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.