DEVELOPERS · OUTSIDE AGENTSComing soon

Register an agent
built anywhere.

Any framework, any model. Zuger checks who stands behind your agent and says so in a credential anyone can check. Your keys stay on your machine.

GET THE MARK

Two tiers.

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

Registered

Free. Prove a domain with a DNS record or a file on your site, or with your own email address at it. The credential says what was checked, and nothing more.

Coming soon

Verified

A business check through Stripe, and a yearly fee in euros invoiced by Zuger Technologies OÜ. The price is not set yet.

Coming soon
  1. Sign up with a passkey

    A developer account has no plan and runs no Zuger agents. It only registers yours.

  2. Prove your domain

    A TXT record, a line in a file on your site, or your own address at the domain. Zuger checks it again every 30 days.

  3. Register your agent

    Its name, what it does, the scopes it declares and its public key.

  4. Get a credential

    Issued to the key you registered, once issuing opens.

The mark itself is being designed. It will be shown here once it is chosen.

YOUR KEYS

Your keys stay
on your machine.

We never see your private key

You send the public half as a JWK. A JWK that carries the private part is refused and never stored.

Approved with a passkey

Your agent makes a key, and you approve it with a passkey on your phone or laptop. It lives 24 hours at most.

Hardware keys

A key in Apple’s Secure Enclave or a TPM can be attested and said so in the credential. Setup guides are coming.

Rotate at any time

The new key replaces the old one, and the old one is revoked in the same step.

Lose the proof, lose the credential

If your domain proof disappears, the agents registered on it lapse until it is back.

Agents never register themselves

A person signs in to register an agent. No route lets an agent make its own account or credential.

REGISTER

The routes.

Switched off today: every route below answers 404 until registration opens.

MethodPathDoes
POST/v1/kya/developersOpen a developer account. A link goes to the address.
POST/v1/kya/domainsProve a domain: dns, well_known or email. The answer says what to publish.
POST/v1/kya/domains/:id/checkLook for the proof now.
POST/v1/kya/agentsRegister an agent on a proven domain.
POST/v1/kya/agents/:id/keysRotate its key.
DELETE/v1/kya/agents/:idRemove it: its keys are revoked and its DID document is gone at once.
POST/v1/kya/keys/delegationsAsk for a 24-hour key to be approved with a passkey.
# POST /v1/kya/agents
{
  "name": "Invoice reader",
  "description": "Reads supplier invoices and drafts entries.",
  "domain": "example.com",
  "publicJwk": { "kty": "OKP", "crv": "Ed25519", "x": "…" },
  "manifest": {
    "does": "Reads supplier invoices and drafts ledger entries.",
    "scopes": ["read:documents"],
    "homepage": "https://example.com/agent"
  }
}

The model and the provider are yours to name or leave out. The answer gives the agent an opaque did:web identifier. Registering costs nothing and issues no credential yet.

LimitValue
Agents for each Registered developer25
Domains for each developer10
Agents registered in an hour5
Agents registered in a day20
Key changes in a day10
Domain proof checked againEvery 30 days

START WITH YOUR PHONE

A key approved
with a passkey.

  1. Your agent makes a key

    An Ed25519 key pair, in memory or your operating system’s key store. It asks for the public half to be approved.

  2. You approve it

    In the Console, with your passkey. What you sign commits to that exact key, those scopes and that expiry, so nothing can be swapped in.

  3. It works for 24 hours

    A stolen key dies within a day. Registered agents in good standing renew without a tap; Verified agents need one, or a standing window of up to seven days.

  4. Move to hardware when asked

    When the platforms you work with ask for an attested key, move to the Secure Enclave or a TPM.

ADD VERIFICATION

Check an agent
before you let it in.

Free, with no account. Send the signed request you received; the answer is the first check that failed, or ok.

# POST /v1/kya/verify  (coming)
{ "valid", "code", "reasons", "issuer", "assurance", "scopes", "agent", "reputation" }
CodeMeans
missing_signature · missing_credentialNothing to check.
untrusted_issuer · bad_issuer_signatureThe issuer is not trusted, or its signature does not verify.
expired · revokedNo longer valid.
key_mismatch · replayNot signed by the credential’s key, or not fresh.
out_of_scopeValid, but not allowed to do this.
okEvery check passed.

Agents cannot vouch for themselves

The verifier refuses a request whose caller is the agent being checked.

Nothing to enumerate

An unknown id answers like a revoked one, and undisclosed claims are never returned.

Declared, not enforced

An outside agent’s scopes are declared by its operator. The answer says so, and grants nothing on them.

The verifier is built and switched off. This section will say when it answers.

THE BADGE

A badge on your site,
checked live.

Drawn after a live check

The badge is drawn by your page after a fresh check from zuger.ai, never sent by an agent and never a picture.

Fails safe

When the check fails, it shows Unverified or Revoked, never the mark.

A picture proves nothing

Only trust a badge inside an app that checks it, or on zuger.ai.

Verified by ZugerExample

The snippet will be published here when the badge is live. The mark and its rules

SDK AND CLI

Coming soon.

WhatNameStatus
TypeScript@zuger/agent-protocolComing soon
Pythonzuger-agent-protocolComing soon
Command linezuger-kya · zuger-zapComing soon

None is published yet. Until they are, the routes above are the interface.

Built on open standards

The protocol underneath.

How the handshake works, and every standard it stands on.

The handshakeDeveloper docs