Beta · Identity for AI agents

Not a borrowed name.
Its own identity.

Atmark gives each AI agent an identity of its own.That identity comes with its own name@atmark.ai address.

Get started Log in

Atmark is in beta. You can create agents and tokens as soon as you sign up; sending to outside recipients opens once an operator has reviewed your organization.

Agent identity

Scout

scout@atmark.ai

DID
did:web:id.atmark.ai:agents:7c21…f5a1
Issued
2026-09-24
Status
Published
Reverse · passport.jwsEdDSA
Public key
z6MkqR8v…Vt9x
{
  "type": "AtmarkAgentPassport",
  "status": "published",
  "credentialSubject": {
    "name": "Scout",
    "address": "scout@atmark.ai"
  }
}
Owner
Example Labs Private
Example card. Organization names are never put in the public documents.

What each agent gets

What the identity does

  1. Every send goes through one gate

    Anything blocked by the suppression list, a sending limit or your policy stays put.

  2. Off the list, it doesn’t go out

    New agents start with an empty allowlist. Anyone off the list is refused; blocked inbound mail is quarantined and logged.

  3. Stop it any time, keep the record

    One kill switch halts sending for a single agent or your whole organization.

Sending gateExample
From
scout@atmark.ai
To
partner@example.com
Subject
Time to meet next week?
Blocked · not on allowlist

This recipient isn’t on the owner’s outbound allowlist, so the message didn’t go out. The decision is logged.

Recipients on the list go straight through. The owner edits the list in the console.

What you can check today

  • id.atmark.ai/agents/…/did.json

    The DID resolves

    A published did.json is a public HTTPS document, read the standard did:web way.

  • {"alg":"EdDSA","typ":"JWT"}

    The passport signature checks out

    passport.jws is a standard JWT. Check its signature and expiry against the key in did.json.

  • denied: recipient_not_allowlisted

    Actions are on record

    Gate decisions and console actions are kept as audit records you can review in the console.

How it works

  1. Sign up

    Enter your email and an organization name, then open the confirmation link we send.

  2. Create an agent

    Its identity and its name@atmark.ai address are issued together. Publish the identity from the console after review.

  3. Connect the token

    Use remote MCP or the REST API. The token is shown once, when you create it.

  4. Set the policy

    Choose who it can write to and hear from in the console. Nothing goes out to anyone off the list.

Start with the beta.

Outside sending opens after an operator reviews your sign-up. In the meantime you can create agents and tokens and get your integration ready.

Get started Log in