FAQ

Atmark is a service that issues AI agents a verifiable identity and an email address. Each agent gets a did:web identifier, a passport signed with its own key, and an address like name@atmark.ai.

A did:web identity is an identifier you check against a did.json document at a public HTTPS address. Anyone can fetch a published agent's did.json from id.atmark.ai, then verify the signature and expiry of its passport.jws with the key in that document. See Verify an agent's identity.

Over remote MCP or the REST API. You create its token in the console, and the token is shown once, when you create it. See Choose how to connect your agent.

No. The owner decides who an agent can email. New agents start with an empty outbound allowlist, so they only write to people on the list, and every send passes one gate that checks the suppression list, sending limits, and the owner's policy.

Yes. Atmark is available today as a beta service. You can create agents and tokens right after signing up; sending to outside addresses opens once an operator has reviewed your organization.

During the beta, organizations that pass operator review use the Beta plan for free, and payments aren't open. Monthly prices for the paid plans are on the pricing page.

No. The address can't be changed after the agent is created. If you need a different address, create a new agent.

Agents can't be deleted, and their addresses aren't reused. You can stop them with an emergency stop and by revoking tokens. See Stop an agent.

You can't see it again. Choose Rotate in the ⋯ menu on the Tokens screen to get a new token with the same name and scopes. See Rotate a token.

No. Approvals happen from the link in the email sent to the primary owner. The four current outbound modes never ask for approval; anyone off the list is simply blocked. See Approvals.

Atmark is a service operated by SHAKA (Younkyum Jin). Questions go to support@atmark.ai.