SIGN IN WITH ZUGERComing soon

Sign in with Zuger,
for agents.

Sites that accept Sign in with Zuger can let verified agents in.

HOW IT WILL WORK

Three steps, one token.

01

Your site asks

An agent arrives. Your site, or our widget, asks it to sign in with Zuger.

02

The agent shows its credential

It shares only what your site asks for, and proves the credential is its own with its key.

03

Your site gets a token

Checked by Zuger’s verifier or by the SDK on your own server, with the claims below.

THE TOKEN

What your site will receive.

ClaimWhat it says
agent_didWhich agent this is.
operatorWho runs it.
assuranceIts tier: Registered or Verified.
scopesWhat it may do.
reputationIts reputation, and as of when.
key_protectionHow its key is held.
acts_forWho 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

You decide who comes in.

A minimum tier

Let in only Verified agents, or Registered ones too.

A minimum reputation

Set the floor an agent must reach.

The skills you accept

Only agents whose skills you allow.

Rate limits

How often one agent may sign in.

Revocation honoured

A revoked agent cannot sign in once the status list says so.

No account for your users

Your site needs no Zuger account for the people who use it.

WHAT IT WILL COME WITH

Drop it in.

Planned

A widget

A small script for your sign-in page.

Planned

Server SDKs

TypeScript and Python, to check the token on your own server.

Planned

Signed requests too

Agents that sign each request with Web Bot Auth can be checked the same way.

STANDARDS

What it is built on.

From the platform’s standards registry. Supported means the code implements it and passes its check. It does not mean the feature is live.

StandardVersionStatusWhat it does
OpenID for Verifiable Presentations—PlannedPresenting 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-19SupportedThe 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 requestsdraft-ietf-webbotauth-httpsig-protocol-00 and draft-meunier-webbotauth-httpsig-directory-00SupportedOther agents' signed requests verified by verifyAny(), named by their key directory. It grants nothing.
HTTP Message SignaturesRFC 9421 (Ed25519 only)SupportedProof of possession on each request an agent sends to a receiver that asked for it (label kya).
Token Status Listdraft-ietf-oauth-status-list-21SupportedRevocation of Zuger's credentials: one bit per credential, checked by every verifier.

QUESTIONS

Questions, answered.

Does it get an agent past my CAPTCHA?

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.

Does my site need a Zuger account?

Your site registers as a developer account, with a passkey. The people who use your site need nothing.

Is it the same as signing in to Zuger?

No. People sign in to the Console with their passkey. Sign in with Zuger is for agents, with a key of its own.

Free plan · No card

Let good agents in.

Sign in with Zuger is planned. Tell us about your site.