# Give an AI agent its own email inbox

An agent with its own inbox can sign up for things, read the code that comes back and get on with the job. First pick the service, then open the inbox.

Updated: 18 November 2026 · Topic: Email inbox

## The numbers

From the drives of 246 products, 1 Oct to 18 Nov 2026. Each one links to its definition and evidence.

- Sign-up mails that reached our inbox within 10 seconds: 45 of 95
- Sign-up mails that reached it within a minute: 93 of 95
- Products our agent verified without a browser: 11 of 95

[Every fact](https://agentdrives.com/data/facts?via=md)

## The short answer

Give the agent an inbox of its own, at a service it can sign up for over an API. At [AgentMail](https://agentdrives.com/tools/agentmail?via=md), one call returns an account, an inbox and an API key, and an emailed code confirms it. Our agent was in and holding a key in 2 minutes, with no browser and no person. AgentMail is at level 5, Autonomous.

## Your inbox or its own

Its own. Connected to your mailbox, an agent reads everything in it, and a person has to sign in to grant the access. An inbox of its own holds only the agent's mail, and the agent can open it without you.

## Which inbox service

Pick one your agent can sign up for without a person. Of these six, our agent did that at AgentMail.

| Service | What it offers | Our drive |
|---|---|---|
| [AgentMail](https://agentmail.to/) [1] | An inbox for each agent, made with one API call | [L5 · Autonomous](https://agentdrives.com/tools/agentmail?via=md). Signed up and worked with no person (31 Oct 2026) |
| [Mailtrap](https://mailtrap.io/agent-inbox/) [2] | Agent Inbox: an address per agent for inbound mail | [L1 · Needs a person](https://agentdrives.com/tools/mailtrap?via=md). Stopped at sign-up: reCAPTCHA checkbox on the sign-up form (6 Oct 2026) |
| [Nylas](https://www.nylas.com/products/agent-accounts/) [3] | Agent Accounts: an inbox and a calendar per agent, in one API call | Not driven yet |
| [mails.ai](https://mails.ai/) [4] | An address per agent in one API call, with limits on who it emails | Not driven yet |
| [Shipmail](https://shipmail.to/) [5] | Business email on your own domain, with an API for agents | Not driven yet |
| [DevInbox](https://devinbox.io/) [6] | Closed to new sign-ups; shuts down on 31 Dec 2026 | Not driven yet |

What each offers is from its own site, read on 4 Nov 2026. For a calendar as well as an inbox, Nylas puts both in one agent account. For people and agents on your own business domain, Shipmail hosts the mail.

## The steps our agent took at AgentMail

In the order of our drive on 31 Oct 2026. Each step is in the words of the drive record.

1. **Read the onboarding block.** llms.txt has an agent onboarding block (sign-up API, MCP endpoint and x-api-key header); docs pages as .md and via Accept: text/markdown; OpenAPI 3.1.0 with 180 operations; AsyncAPI for WebSockets. [Drive record: how an agent connects](https://agentdrives.com/tools/agentmail?via=md#connect)

2. **Sign up with one call.** POST /v0/agent/sign-up returned an org, an inbox and an API key in one call. [Drive record: getting in](https://agentdrives.com/tools/agentmail?via=md#get-in)

   ```
   curl -s https://api.agentmail.to/v0/agent/sign-up \
     -H "content-type: application/json" \
     -d '{"human_email": "you@example.com",
          "username": "agent"}'
   ```

3. **Confirm with the mailed code.** The 6-digit code mailed to the agent's inbox within seconds verified the org via POST /v0/agent/verify ({"verified":true}). [Drive record: getting in](https://agentdrives.com/tools/agentmail?via=md#get-in)

4. **Keep the key from the answer.** The API key comes in the sign-up answer; scoped keys are created, used and revoked through /v0/api-keys. [Drive record: getting in](https://agentdrives.com/tools/agentmail?via=md#get-in)

5. **Connect the MCP server.** Use the hosted MCP server https://mcp.agentmail.to/mcp with header x-api-key: <your key>; no OAuth needed. [Drive record: what an agent can do](https://agentdrives.com/tools/agentmail?via=md#use)

6. **Read new mail without a public address.** For events without a public URL, use WebSockets (wss://ws.agentmail.to/v0?api_key=…) or a polling webhook created a few minutes ahead. [Drive record: tips for agent builders](https://agentdrives.com/tools/agentmail?via=md#tips)

7. **Mind the first hour's sending limit.** A new org may email only 3 new recipients in its first hour (5 in 24 h); replies to people who wrote to you don't count, and the 429 carries Retry-After. [Drive record: tips for agent builders](https://agentdrives.com/tools/agentmail?via=md#tips)

Expect some addresses to be refused. The first address our agent gave was turned down with `403 Domain is forbidden`; an address on another domain went through.

## How long the sign-up mail takes

Fast. Of the products whose sign-up mail we timed, 45 of 95 reached our inbox within 10 seconds and 93 of 95 within a minute. The slowest took 88 seconds.

| Mail had | Products | Median wait | Without a browser |
|---|---|---|---|
| A code | 31 of 95 | 11 s | 3 of 31 |
| A link | 44 of 95 | 11 s | 8 of 44 |
| A code and a link | 20 of 95 | 9 s | 0 of 20 |
| Any | 95 | 10 s | 11 of 95 |

The wait is not what stops an agent; the next step is. Where the mail carried a code only, our agent finished without a browser at 3 of 31: the code had to be typed into a web page. AgentMail takes its code over the API, so nothing needs a page.

## What your agent should do with its inbox

1. **Poll, don't sleep.** Check for new mail every few seconds and give up after 88 seconds, the slowest we saw. A WebSocket or a webhook beats both.

2. **Match the mail to the sign-up.** Read the sender and the subject before you take a code, so a mail from an earlier attempt isn't used.

3. **Prefer the code to the link.** A link often opens a page that wants a browser. A code can go straight into an API call.

4. **Keep one inbox per agent.** Then each agent reads only its own codes, and one agent's mail never ends up in another's sign-up.

## Check it yourself

1. **Start from nothing.** No account and no key. Ask an agent to open an inbox from the provider's docs alone.

2. **Time the first mail.** Have the agent sign up somewhere with its new address and note how long the code takes to arrive.

3. **Count the times a person had to step in.** Each one is where an agent on its own stops. [Test your product with an AI agent](https://agentdrives.com/guides/test-your-product-with-an-ai-agent?via=md) has the full list of checks.

[Written with AI](https://agentdrives.com/method?via=md#notes) from our drives and the vendors' own docs.

## Products in this guide

1, by level

- [AgentMail: L5 Autonomous](https://agentdrives.com/tools/agentmail?via=md) AgentMail Email infrastructure Find Docs it can act on Get in Try first, claim later, key by API Use 100% of the work Pay Can pay on its own Leave Nothing to cancel **L5** Autonomous Driven 31 Oct 2026

## Fixed it? Drive it again

- **Free, after a fix.** Tell us what you changed in your account and our agent drives it again, up to twice a year.
- **Watch, $49 a month.** A full private drive every month, with every fix and the one that matters most first.

[Tell us you fixed it](https://agentdrives.com/app/products) · [About Watch](https://agentdrives.com/owners#watch)

## Where our agent stopped in each

1 product in this guide, by level.

- [AgentMail](https://agentdrives.com/tools/agentmail?via=md): L5 Autonomous

## Pages this guide cites

1. [AgentMail](https://agentmail.to/)
2. [Mailtrap](https://mailtrap.io/agent-inbox/)
3. [Nylas](https://www.nylas.com/products/agent-accounts/)
4. [mails.ai](https://mails.ai/)
5. [Shipmail](https://shipmail.to/)
6. [DevInbox](https://devinbox.io/)

## Asked about this guide

**Which email inbox service can an AI agent sign up for on its own?**

AgentMail, of the six we compared. Our agent signed up, confirmed by code and got a key there with no person. At Mailtrap it stopped and a person had to step in.

**Can an AI agent have its own email address?**

Yes. At AgentMail an agent opens one itself with one API call, then confirms it with a code sent by email. No browser or person is needed.

**How long does a sign-up code take to arrive?**

Seconds, mostly. 93 of 95 of the sign-up mails we timed came within a minute, half of them within 10 seconds.

**Why use a code rather than a link?**

A link usually opens a web page, which needs a browser. A code can be sent back to the service in an API call.

Previous guide: [Test your product with an AI agent: the nine checkpoints](https://agentdrives.com/guides/test-your-product-with-an-ai-agent.md?via=md)

## More from the drives

- [Make your SaaS agent-ready: the whole path, step by step](https://agentdrives.com/guides/make-your-saas-agent-ready?via=md) (Guide · The whole path): Docs, sign-up, the key, MCP, paying and leaving: what an agent needs at each step, with the fix for each.
- [An MCP server is not a way in for AI agents](https://agentdrives.com/guides/an-mcp-server-is-not-a-way-in?via=md) (Guide · MCP): Most products have an MCP server. What an agent still needs behind it: an account, a key and a sign-in it can finish.
- [How AI agents pay for software: x402, MPP and checkouts](https://agentdrives.com/guides/how-ai-agents-pay-for-software?via=md) (Guide · Paying): Card checkouts, x402 and MPP: what an agent can pay with today, and what most products ask instead.

[All research](https://agentdrives.com/research?via=md)
