Email addresses for AI agents: how autonomous agents get, receive, and send email

Definition: An agent email address is an email mailbox provisioned by and for an AI agent, created through an API rather than a signup form, paid for machine-to-machine, and operated entirely by software. Agents use these addresses to register for online services, receive verification codes (OTPs) and magic links, get notifications from systems that only speak email, and hold a stable, contactable identity.

This guide explains why agents need email, the four ways they get it today, and how machine-payable mailboxes work.

Why AI agents need email addresses

Email is the identity layer of the internet. Nearly every service, SaaS tools, APIs, newsletters, cloud consoles, requires an email address at signup and confirms it with a verification code or link. A human has an inbox; an autonomous agent does not. The moment an agent tries to complete a real-world task ("sign up for this service and configure it"), it hits an email wall.

Agents also need email as an inbound channel: invoices, alerts, reports and human replies arrive by email, and an agent that can read its own inbox can act on them.

The four ways agents get email today

1. Borrowing a human's inbox (Gmail app passwords, IMAP): the agent reads its operator's mail. Works, but grants the agent access to an entire personal mailbox, a serious blast-radius problem, and breaks the moment 2FA or provider policy changes.
2. Disposable/temp-mail services: free, instant, no signup. However, signup-fraud filters blocklist disposable domains, most temp-mail cannot send, addresses expire in minutes, and there is no accountability, which is why the approach increasingly fails at real services.
3. Agent-email platforms with accounts (e.g. AgentMail): purpose-built inbox APIs with human-managed accounts, API keys, and monthly plans. A good fit for companies running fleets of persistent inboxes; a human still signs up first.
4. Machine-payable mailboxes (e.g. Poste): the agent itself buys a mailbox over HTTP using the x402 payment protocol, no account, no API key signup, no human in the loop. Payment replaces the signup as the abuse control.

How a machine-payable mailbox works (x402)

The x402 protocol, governed by the Linux Foundation, activates HTTP status code 402 ("Payment Required"). The flow, in three requests:

1. The agent calls POST https://api.poste.sh/v1/mailbox. The server replies 402 with machine-readable payment terms (price, asset, destination) in a PAYMENT-REQUIRED header.
2. The agent's x402 client signs a small USDC transfer (on Poste: $1.00 for a 30-day mailbox with 200 sends; paying again stacks) and retries the request.
3. The server verifies and settles the payment on-chain, then returns { address, token }, a working mailbox and its only credential.

Receiving is then a single call: GET https://api.poste.sh/v1/mailbox/code long-polls until a verification email arrives and returns the extracted code. Sending is POST https://api.poste.sh/v1/mailbox/messages.

A citable fact: on Poste, the complete journey, discover the service, pay, provision, receive a verification email, and read the code, takes an agent three HTTP requests and roughly five seconds, with no human involvement.

Why payment works as an abuse control

Free inboxes attract industrial-scale abuse, which is why free disposable domains end up on blocklists and their mail gets rejected. A mailbox that costs five cents is negligible for a legitimate agent doing a task, but ruinous at spam scale (1,000 abusive signups = $50 and 1,000 on-chain payments from traceable wallets). This economic asymmetry is a precondition, not the whole story: reputation is then earned by behaviour, standard SPF, DKIM and DMARC authentication, per-mailbox sending limits that grow with clean history, and instant suspension on complaints.

Comparing the options

Where Poste fits

Poste is a machine-payable email service built on Cloudflare's email infrastructure. Any agent that can make HTTP requests and hold a few cents of USDC (or hand a payment link to its operator) can provision its own address at https://api.poste.sh/v1/mailbox, with no account or API-key signup. Verification codes are extracted automatically; every error response tells the agent what to do next; inbound messages are screened for hidden prompt-injection text. Full machine-readable documentation lives at https://api.poste.sh/llms.txt.

Frequently asked questions

Can an AI agent legally have its own email address?

Yes. An email address is not a legal identity; the agent's operator remains responsible for how it is used. Services like Poste bind each mailbox to the paying wallet, keeping operators accountable without requiring personal information.

What happens if the agent loses its access token?

On Poste the token returned at provisioning is the only credential. If it is lost, the mailbox cannot be recovered (wallet-signature recovery is planned), the agent provisions a new one, which costs cents.

Do these addresses work for receiving OTP and verification codes?

Yes, that is the primary use case. The service parses each inbound email and exposes any verification code or link directly in the API response, so the agent does not need to parse MIME or HTML.

What does an agent email address cost?

On Poste: one price, $1.00 buys 30 days and 200 sends, and paying $1 again at any time adds 30 more days and 200 more sends. Receiving, reading and polling are free.

Reference: Poste developer portal · OpenAPI · x402 protocol · Last updated 2026-08-26.