Your site asks
An agent arrives. Your site, or our widget, asks it to sign in with Zuger.
SIGN IN WITH ZUGERComing soon
Sites that accept Sign in with Zuger can let verified agents in.
HOW IT WILL WORK
An agent arrives. Your site, or our widget, asks it to sign in with Zuger.
It shares only what your site asks for, and proves the credential is its own with its key.
Checked by Zuger’s verifier or by the SDK on your own server, with the claims below.
THE TOKEN
| Claim | What it says |
|---|---|
agent_did | Which agent this is. |
operator | Who runs it. |
assurance | Its tier: Registered or Verified. |
scopes | What it may do. |
reputation | Its reputation, and as of when. |
key_protection | How its key is held. |
acts_for | Who it acts for. Off by default: only when the agent’s company allows it for your site. |
{
"agent_did": "did:web:agent.example.com",
"operator": "Example GmbH",
"assurance": "verified",
"scopes": ["read:documents"],
"reputation": { "score": "…", "as_of": "…" },
"key_protection": "…"
}YOUR RULES
Let in only Verified agents, or Registered ones too.
Set the floor an agent must reach.
Only agents whose skills you allow.
How often one agent may sign in.
A revoked agent cannot sign in once the status list says so.
Your site needs no Zuger account for the people who use it.
WHAT IT WILL COME WITH
A small script for your sign-in page.
TypeScript and Python, to check the token on your own server.
Agents that sign each request with Web Bot Auth can be checked the same way.
STANDARDS
From the platform’s standards registry. Supported means the code implements it and passes its check. It does not mean the feature is live.
| Standard | Version | Status | What it does |
|---|---|---|---|
| OpenID for Verifiable Presentations | — | Planned | Presenting an agent's credential to a site that asks, for "Sign in with Zuger". Sign in with Zuger (milestone G2). |
| SD-JWT-based Verifiable Credentials (SD-JWT VC) | draft-ietf-oauth-sd-jwt-vc-19 | Supported | The format of Zuger's agent credentials (kya/agent/v0.1) and of outside agents' (kya/ext-agent/v0.1): issued and verified by the library. No credential is issued in production yet (milestone A3). |
| Web Bot Auth: verifying signed agent requests | draft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00 | Supported | Other agents' signed requests verified by verifyAny(), named by their key directory. It grants nothing. |
| HTTP Message Signatures | RFC 9421 (Ed25519 only) | Supported | Proof of possession on each request an agent sends to a receiver that asked for it (label kya). |
| Token Status List | draft-ietf-oauth-status-list-21 | Supported | Revocation of Zuger's credentials: one bit per credential, checked by every verifier. |
QUESTIONS
No. Your site decides whom it lets in. Sign in with Zuger tells you who an agent is, so you can let it in on purpose.
Your site registers as a developer account, with a passkey. The people who use your site need nothing.
No. People sign in to the Console with their passkey. Sign in with Zuger is for agents, with a key of its own.
Sign in with Zuger is planned. Tell us about your site.
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.