Why AI agents need their own email infrastructure
Email is the universal API between businesses - and agents are terrible tenants in human inboxes. Why borrowing a Gmail account does not scale, and what agent-native email looks like.
Dvir Atias
Founder
Every business process eventually touches email. Invoices arrive by email. Suppliers confirm orders by email. Customers escalate by email. If you are building an agent that participates in real workflows, it will need to send and receive email - not as a nice-to-have, but as the primary channel the rest of the world already uses.
The borrowed-inbox problem
The default hack is to give the agent a human's mailbox: an OAuth grant against Gmail or Outlook, plus IMAP polling. It breaks down fast:
- Identity. The agent sends as a person. Replies, threading, and deliverability reputation all tangle with a human account.
- Multiplicity. One agent per OAuth grant is fine. A thousand customer-specific agents, each needing its own address, is not something consumer mail providers are built for.
- Consent screens and token expiry. Every re-auth is a human interruption in a system that is supposed to remove humans from the loop.
- Rate limits and TOS. Automated traffic through consumer inboxes gets throttled, flagged, or banned.
What agent-native email looks like
Treat the inbox as an API resource instead of a personal possession:
- Inboxes on demand.
POST /v1/inboxesreturns a working address in milliseconds. Spin one up per agent, per customer, per task - and delete it when the task is done. - Events, not polling. Inbound mail arrives as a webhook or a WebSocket event with the message already parsed. No IMAP, no cron.
- Scoped credentials. Each agent holds a key that can only touch its own inbox. Blast radius of a leak: one inbox.
- Deliverability handled below the API. SPF, DKIM, DMARC, IP reputation, bounce handling - infrastructure concerns, not agent code.
The interesting part
Once inboxes are cheap, patterns emerge that were never practical before: a negotiation agent that opens a fresh address per counterparty, a support fleet where every customer conversation has a dedicated agent behind a dedicated address, a procurement bot that files every vendor thread into its own inbox with full audit history.
That is the bet behind AgenticEmail: email is not legacy - it is the most widely deployed agent-to-world interface that exists. It just needed an API that treats agents as first-class senders and receivers.