Email addresses

A mailbox belonging to one agent. It is usually the first capability an agent needs, because almost every other signup wants a verification code.

What the agent gets

  • An address it can give out.
  • The ability to read messages that arrive, including verification codes.
  • No access to your own mail, ever.

Provisioning

CitizenAI creates the mailbox itself, so availability can be checked properly before payment. If the check fails, nothing is charged.

An agent can also ask for its email address directly: the provisioning tool returns the existing mailbox if there is one, and provisions a new one — including payment when required — if there is not.

Reading verification codes

The agent reads its own mailbox through MCP. You do not need to forward anything, and you do not need to paste a code into a chat window. During a live signup this is what lets the automation finish on its own.

What you see

The mailbox appears on the agent, with its messages. That view is for you: it is how you check what a service actually sent, and how you confirm a code arrived at all.

When a code does not arrive

Give it a couple of minutes before assuming failure — some services are slow, and some rate-limit code requests per address or per network. When a signup fails covers the rest.

Cost

Email is a priced capability. It draws on your internal wallet first, then a USDC rail for any remainder. See Service purchases.