Give your AI agent an inbox in five minutes

Most agents that "do email" today are actually screen-scraping a Gmail account that a human set up by hand. That works for a demo and falls over in production: OAuth tokens expire, one shared inbox becomes a bottleneck, and there is no clean way to give each agent - or each of your users' agents - its own address.

AgenticEmail flips the model: inboxes are a resource you create with an API call, like a database row.

1. Create an inbox

curl -X POST https://api.agenticemail.dev/v1/inboxes \
  -H "Authorization: Bearer $AGENTICEMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "username": "support-agent" }'

The response contains a live address like support-agent@inbox.agenticemail.dev. On paid plans you can attach your own custom domain and the address becomes support-agent@yourdomain.com.

2. Receive mail

You have two options, and they can run at the same time:

• Webhooks - register an HTTPS endpoint and every inbound message is delivered as a signed JSON payload with parsed headers, text, HTML, and attachments.
• WebSocket events - subscribe to the real-time stream and get the same payload pushed to a long-lived connection, useful for agents that are already running.

curl -X POST https://api.agenticemail.dev/v1/webhooks \
  -H "Authorization: Bearer $AGENTICEMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://your-app.com/hooks/email", "event_types": ["message.received"] }'

3. Reply

Sending is one call. Threading headers are handled for you when you pass the message you are replying to:

curl -X POST https://api.agenticemail.dev/v1/inboxes/ibx_123/messages/msg_456/reply \
  -H "Authorization: Bearer $AGENTICEMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text": "Thanks - refund issued, you should see it in 3-5 business days." }'

4. Scope the key

Agents should not hold god-mode credentials. Scoped API keys restrict a key to specific inboxes and specific operations, so a compromised agent can at worst read and send from its own inbox - not touch your whole account.

That is the entire integration: one key, one inbox, one webhook, one send endpoint. If your agent framework speaks MCP, the AgenticEmail MCP server wraps all of the above so your agent can manage its own inbox with natural tool calls.