Pod tenancy for fleets of agent addresses
The identity and email layer for AI agent fleets. Create API inboxes at scale, isolate tenants with Pods, and fan in replies over message.received without polling thousands of boxes.
The problem
Google Workspace and the Gmail API assume human seats and OAuth consent, so you cannot mint hundreds of agent mailboxes from code.
Amazon SES gives cheap send and receive building blocks, but you still own the mailbox store, threading, and per-tenant isolation.
Mailtrap is strong for send and MCP workflows, yet inbound inbox ownership is not the fleet primitive when each agent needs its own address.
Infraforge and Mailforge optimize cold outreach domains, warm-up, and rotation. They are not an agent thread store for product workflows.
Nylas connects human Gmail or Outlook. That fits acting as a person, not provisioning an agent-owned fleet with Pod boundaries.
The solution
AgentMail is the identity and email layer for fleets that need Pod-isolated agent addresses at scale.
API inbox create per agent
Mint a dedicated address per agent with no OAuth seat. Each agent keeps its own threads, reputation path, and audit history.
Pods for per-tenant isolation
Map each customer to a Pod with inboxes, domains, and scoped keys. Use client_id so your tenant id is the Pod lookup key.
message.received webhooks
Fan replies into your runtime in realtime. Agents do not poll thousands of boxes to find the next message.
Custom domains and Enterprise scale
Attach domains with SPF, DKIM, and DMARC. Startup caps at 150 inboxes. Enterprise offers unlimited inboxes and dedicated IPs.
What your agent fleets can do
Provision
Per-agent identity at signup
When a new AI employee or AI SDR spins up, create its inbox in the same API call path as the agent record.
Tenancy
Tenant Pods for multi-customer products
Give each customer a Pod so inboxes, domains, and thread lists stay isolated when one platform serves many fleets.
Realtime
Webhook fan-in without polling
Subscribe once to message.received, route by inbox or Pod, and keep agent loops on events instead of mailbox scrapes.
Reputation
Domain and reputation separation
Separate domains and inboxes so one noisy agent does not take deliverability down for the rest of the fleet.
AgentMail is built to scale.
Redundant infrastructure spanning multiple regions, so a message to your agent lands even when a region does not.
Provision an inbox in milliseconds. Nothing to verify, nothing to wait on.
Typed SDKs, REST endpoints, and webhooks. Your first send goes out the same afternoon.
Wire a Pod, inbox, and webhook
Signatures from https://docs.agentmail.to/documentation/core-concepts/pods and https://raw.githubusercontent.com/agentmail-to/agentmail-python/main/reference.md plus https://raw.githubusercontent.com/agentmail-to/agentmail-node/main/reference.md (retrieved 2026-09-08).
FAQ
Common questions about AgentMail and pod tenancy for fleets of agent addresses.
Give your agents their own inboxes
Free tier. No credit card required. Inboxes ready in under a second.
Subscribe to our weekly newsletter.
© 2026 AgentMail, Inc. All rights reserved.