AgentMail sells email inboxes as an API object. An agent, or the developer behind it, calls one endpoint and gets a working address. It can send, receive threaded replies, fire webhooks and search its own mail. The pitch is "It's not AI for your email. It's email for your AI" (homepage, Oct 2026). The buyers are developers building agents that need an identity on the internet: signing up for services, reading one-time codes, running support or scheduling threads.
The surprising fact is how far it reaches into cold email while its terms prohibit it. AgentMail's sales use-case page promises "personalized outbound at scale". Its deliverability docs recommend sending "100 emails from 100 different inboxes" and rotating "multiple custom domains for your outreach campaigns". Its warmup guide says you can connect AgentMail inboxes "to Instantly and Smartlead for programmatic warm up". Yet the terms of service list "spam, phishing, or unsolicited messaging" as a prohibited use.
- Funding: $6M seed led by General Catalyst, with Y Combinator, Phosphor Capital and angels including Paul Graham and HubSpot's Dharmesh Shah (TechCrunch, 10 Mar 2026)
- Users: "tens of thousands" of humans, "hundreds of thousands" of agent users, 500+ B2B customers (company figures, same article)
- Volume: "100M+ emails delivered" (vendor claim, homepage, Oct 2026)
- Largest claimed deployment: CarEdge with "25,000+ inboxes" (vendor FAQ, unverified)
- Team: 10 (YC profile, Oct 2026)
Who built it
AgentMail was founded in 2025 by Haakam Aujla (CEO, formerly a quant researcher at Optiver), Michael Kim (CTO, formerly on autonomous vehicles at Nvidia) and Adi Singh (formerly an investor at Accel, StepStone and Flex Capital) (YC; The Next Web). It went through Y Combinator's Summer 2025 batch. The Python SDK's first release on PyPI is dated 13 February 2025, and the launch post is dated 8 August 2025.
Growth came from agent frameworks, not sales. TechCrunch reports that user numbers tripled in the week OpenClaw broke out in late January 2026 and quadrupled the next month. AgentMail is now an official OpenClaw plugin and ships installers for Claude Code, Codex, Cursor, Grok and others (llms.txt).
What it sells
From the llms.txt and docs, as of October 2026:
| Primitive | What it does |
|---|---|
| Inboxes | One API call per address; @agentmail.to with no DNS, or custom domains with SPF/DKIM/DMARC configured |
| Messages and threads | Send, reply, forward; automatic threading; quoted-history stripping (extracted_text) |
| Real time | Signed webhooks (received, delivered, bounced, complained, rejected) and WebSockets |
| Pods | Multi-tenant isolation per customer or environment |
| Drafts, labels, lists | Human-in-the-loop review, state tags, allow/block lists |
| Protocols | IMAP and SMTP, a hosted MCP server with OAuth, Python and TypeScript SDKs, CLI |
| Agent self-signup | POST /v0/agent/sign-up returns a key after a human confirms by OTP |
| New in 2026 | AgentID (OIDC sign-in for agents) and Agent Armor (beta prompt-injection screening of inbound mail) |
Idempotency covers creates (inboxes, pods, webhooks, drafts) through a client_id, but not sends. The docs tell you to track message IDs yourself or use drafts (rate limits). There is no dry-run and no per-agent spend cap.
The plumbing is Amazon's. The agentmail.to MX record points to inbound-smtp.us-east-1.amazonaws.com (Amazon SES inbound; DNS lookup, 5 Oct 2026), and the subprocessor list names AWS, Svix for webhooks and Clerk for auth.
Whether outbound mail also leaves through Amazon SES is not stated anywhere. The MX record and subprocessor list make it likely; treat it as unverified.
How it prices
From pricing.md, as of October 2026:
| Plan | Price | Inboxes | Send caps | Custom domains |
|---|---|---|---|---|
| Free | $0 | 3 | 3,000/mo, 100/day | None; "Sent via AgentMail" footer |
| Developer | $20/mo | 10 | 10,000/mo, 1,000/day, 100 per 5 min | 10 |
| Startup | $200/mo | 150 | 15,000/day, 1,500 per 5 min | 150 |
| Enterprise | Custom | Up to unlimited | Custom | Custom; dedicated IPs, EU region, BYO cloud |
On the Startup plan that works out to about $1.33 per inbox. That is below the $2.50–3.90 per mailbox Zapmail charges for Google Workspace inboxes. But these are not Google or Microsoft mailboxes. They sit on AgentMail's own sending infrastructure with "Optimized Shared IPs", which puts them in the private-SMTP class of Google vs Microsoft vs SMTP, not alongside the Workspace inboxes that ESP matching depends on. The docs list Startup at 150,000 emails a month (rate limits); the pricing page shows no monthly cap.
Who uses it and why
The customer page lists 13 stories. Most are not about outbound. Browser Use gives every cloud session an inbox for sign-ups. Alchemy's AgentCard gives every paying agent one. Opendoor is moving its closing workflow onto it, Lanesurf runs freight conversations through "hundreds of programmatic inboxes", and Balance, an EU accounting agent, chose it for EU hosting.
The exception matters for this hub. AiSDR is profiled as "a fully autonomous AI SDR" running "hundreds of AgentMail inboxes in production, thousands of emails per week, no human in the loop" (case study, May 2026). That is cold outbound by any reasonable reading.
Where it is strong
- Primitives designed for agents. Inbox-as-object, threading, signed webhooks, pods and an OAuth MCP server are what the Sending engine as an API opening asked for, and they ship on a free tier.
- Distribution through agent tooling. Plugins for OpenClaw, Cursor, Codex, Claude Code and Grok, plus an agent self-signup endpoint, let it acquire users without sales.
- Content engine. 203 sitemap URLs, 81 of them updated in September 2026 alone, a 26.6 KB llms.txt, and an AEO page farm under
/blog/info/that tells AI agents to query pages with?q=(crawl data; see llms.txt, pricing.md and AI crawlers). - Compliance basics. SOC 2 Type II, HIPAA BAA on enterprise (llms.txt).
Where it is weak
- Policy contradiction. It markets outbound and teaches rotation, but bans "unsolicited messaging". A customer doing cold outreach cannot know where the line is until an account is shut.
- Shared reputation. The sales page says each agent gets "its own IP and domain reputation"; the pricing page says shared IPs below enterprise. One bad tenant can hurt others.
- Abuse surface. Agents can sign themselves up. TechCrunch reports that unverified agent inboxes are capped at 10 emails a day, plus bounce monitoring and keyword sampling, but those controls are thin for a fleet product.
- Copyable. Nylas launched Agent Accounts in June 2026 with a free tier identical to AgentMail's: 3 inboxes, 3,000 emails, 3 GB. See Nylas and The agent email market.
No revenue figure has been published. As arithmetic only: 500 customers on the $20–200 self-serve plans would come to $0.1–1.2M a year. Enterprise deals such as Opendoor or CarEdge could be larger, and none are priced publicly.
Trajectory
AgentMail is turning from an inbox API into an agent identity layer: AgentID for sign-in, x402 and mpp API subdomains for machine payments (docs on x402 and MPP), and Agent Armor for inbound safety. That moves it further from cold email, not closer. The outbound customers it already has are a liability it will eventually have to police or price.
What this means for an entrant
- Do not compete on the inbox primitive. AgentMail, Nylas, Cloudflare Email Service and Resend all give agents addresses for close to free. The scarce thing is permission to send cold mail and the reputation to land it.
- Take the customers its terms reject. AI SDR builders like AISDR need an engine whose rules say yes to B2B cold outreach under conditions: caps, suppression, legal basis per recipient (EU-native compliant outbound, Governed volume for sales teams).
- Copy the developer surface. An agent self-signup endpoint, an OAuth MCP server, a full llms.txt and per-framework install pages cost little to build and are now expected (Sending engine as an API).
- Integrate, do not fight. Read AgentMail and Nylas inboxes into a The reply desk through webhooks; agent fleets create threads that humans still have to review.
- Watch its enterprise tier. Dedicated IPs, EU region and white-label at enterprise make it a platform an AI SDR company could build on. If its terms soften on cold outreach, it becomes a direct competitor to Inbox & domain infrastructure vendors.