AgentMail Pricing Review (2026): All 4 Tiers, Real Per-Email Math, and the Cliffs

If you searched for "agentmail pricing" you want one of three things: a number, the math at your volume, or a sanity check before sales blocks something behind a "contact us" button. This walks all four tiers with current limits, names what triggers the next jump, and shows where AgentMail's pricing model is cheap (multi-agent inbox use cases) versus where it gets expensive (high-volume transactional). One disambiguation note first: bmail.ag is a separate encrypted-email product, not AgentMail. If you typed "bmail.ag pricing" you are looking at end-to-end encrypted mail, not AI-agent infrastructure. Skip to the bottom for that.

Pricing accurate as of May 2026; check the AgentMail pricing page for current rates.

TL;DR

AgentMail bills a flat monthly fee per tier ($0 / $20 / $200 / custom Enterprise), not per-email or per-inbox. Every tier includes the MCP server and inbound email. The model is cheap when you need many inboxes (multi-agent fleets); it gets expensive when you need volume transactional send (Resend Scale at 150K runs about $135 versus AgentMail Startup at $200, and Amazon SES base is closer to $15 at the same volume).

All four tiers, exact limits

Free, $0/month (no card required)

• 3 inboxes
• 3,000 emails/month with a 100/day hard cap
• 3 GB storage
• 0 custom domains
• 2 team members, 3 inbox pods, 2 webhook endpoints
• MCP server: included
• Inbound email: included
• SOC 2 report: no
• Dedicated IP: no

Developer, $20/month

• 10 inboxes
• 10,000 emails/month, no daily cap
• 10 GB storage
• 10 custom domains
• 2 team members, 10 inbox pods, 2 webhook endpoints
• MCP server: included
• Inbound email: included
• SOC 2 report: no
• Dedicated IP: no
• Email support

Startup, $200/month

• 150 inboxes
• 150,000 emails/month, no daily cap
• 150 GB storage
• 150 custom domains
• 10 team members, 150 inbox pods, 10 webhook endpoints
• MCP server: included
• Inbound email: included
• SOC 2 Type I report: yes
• Dedicated IP: available, but requires contacting sales (no published price)
• Slack channel support

Enterprise, custom pricing

• Inboxes, emails, storage, custom domains, team members: all custom
• White-label platform: yes
• EU region cloud deployment: yes
• Bring-your-own-cloud: yes
• OIDC/SAML SSO: yes
• Dedicated Technical Account Manager: not publicly disclosed

Every tier includes threads, labels, attachments, drafts, scheduled send, Python + Node.js SDKs, multi-factor auth, and social SSO.

The pricing math

Per-inbox cost at full tier utilization:

• Free: $0/inbox (3 inboxes)
• Developer: $2.00/inbox (10 inboxes at $20)
• Startup: $1.33/inbox (150 inboxes at $200)

Per-email cost at full tier utilization:

• Free: $0/email (3,000/mo capacity)
• Developer: $0.0020/email or $2.00 per 1,000 (10,000/mo capacity)
• Startup: $0.0013/email or $1.33 per 1,000 (150,000/mo capacity)

For reference, an equivalent 150 Google Workspace mailboxes at $14/inbox/month is $2,100/month. AgentMail Startup at $200/month is roughly one-tenth the cost when the workload is "many discrete agent inboxes." The model is genuinely competitive for that use case.

What triggers the next jump

The most expensive transitions are the cliffs between tiers, not the per-email rates:

• Need 4-10 inboxes: you are on Developer at $20/month even if you only use 4. There is no intermediate tier. A 4-inbox project pays the same $20 as a 10-inbox project.
• Need 11-150 inboxes or more than 10,000 emails/month: you jump to Startup at $200/month. The 10x price jump between Developer and Startup is the biggest cliff in the lineup.
• Need a dedicated IP, EU region deployment, white-label, or SAML SSO: you contact sales. No published price.
• Need volume above 150,000 emails/month: Enterprise. No published guidance for 500K, 1M, or 5M tiers.
• Hit your monthly email cap: API returns errors. Overage is not automatic billing; sends hard-cut until you upgrade or the month resets.

The hard-cut overage model is meaningfully different from per-email transactional providers (SendGrid, Mailgun, Postmark) where overage bills automatically at a published per-1,000 rate. AgentMail forces a tier-upgrade decision rather than letting the bill creep.

Where AgentMail pricing works (target audiences)

The pricing model is competitive when these are true at the same time:

• The workload is many agent inboxes, not high-volume broadcast send.
• Inbox isolation matters more than per-email cost (each agent gets its own discrete inbox with threading).
• The team is below 150 inboxes and below 150,000 emails/month combined.
• MCP and inbound email are first-class requirements (both included on every tier).
• You can prototype on Free without a credit card.

Specifically: customer support copilots, recruiting agents handling candidate replies, inbound lead qualifiers, scheduling bots that negotiate over email, multi-agent product teams running 10-150 agents in parallel.

Where AgentMail pricing breaks (volume cliffs and hidden costs)

The pricing model breaks down when:

• Your workload is high-volume outbound transactional. AgentMail Startup at $200 per month for 150,000 emails works out to $1.33 per 1,000. Resend, SendGrid, Mailgun, and Amazon SES all price below $1.00 per 1,000 at equivalent volumes (often well below). The per-email gap widens further at 500K+/mo where AgentMail requires Enterprise pricing.
• You need 4-9 inboxes and would otherwise prefer a $5-10 tier. The $0-to-$20 cliff is the entry cost.
• You need a dedicated IP for sender-reputation control. Available only on Startup at $200/month, and even then behind a "contact sales" gate with no published price.
• Your team has more than 2 engineers and you are on Free or Developer. Both cap at 2 team members.
• You need EU data residency, OIDC/SAML SSO, or white-label. Enterprise-only with no published price floor.
• Your daily sending needs exceed 100 emails on the Free tier. The hard cap blocks any meaningful automated agent volume.

AgentMail vs other email APIs at equivalent volumes

The comparison below is for raw sending cost only. AgentMail's inbox provisioning, inbound, MCP, and threading are out of scope for pure transactional providers, so this is an apples-to-pears comparison if your workload needs those primitives.

• At 10,000 emails/month: AgentMail Developer $20 ($2.00/1K) versus Resend Pro $20 (50K included so effectively $0.40/1K), SendGrid Essentials $19.95 (50K included), Mailgun Basic $15 (10K included with $1.80/1K overage), Postmark Pro $16.50 (10K included with $1.30/1K overage), Amazon SES base $1.00 (with 1 dedicated IP + VDM about $26.65). AgentMail Developer is competitive at exactly 10K but does not scale into the next band.
• At 50,000 emails/month: AgentMail Startup $200 (Developer caps at 10K) versus Resend Pro $20 (still within 50K cap), SendGrid Essentials $19.95, Mailgun Foundation $35, Postmark Pro about $68.50 with overage, Amazon SES about $33.45 with 1 IP + VDM. AgentMail is 4 to 10 times more expensive on raw send economics here.
• At 150,000 emails/month: AgentMail Startup $200 ($1.33/1K) versus Resend Scale around $135 ($90 base for 100K + 50K overage at $0.90/1K), SendGrid (volume-band pricing varies; Essentials caps below this), Mailgun Foundation around $165 with overage or Scale around $145, Postmark Basic with overage about $267 (the only one materially more expensive than AgentMail), Amazon SES base around $15.

The pattern is consistent: AgentMail's per-email cost is competitive only at low volume on the Developer tier or at the high end of Startup where the 150 inboxes deliver real value. Outside that window, transactional-first providers win on per-email math.

Note on competitor pricing changes: Resend restructured its Scale tier in October 2024 (Scale starts at 100K for $90 and replaces Pro plans above 100K). Mailgun doubled its Flex pay-as-you-go rate from $1.00 to $2.00 per 1,000 on December 1, 2025. Postmark restructured Pro/Platform in August 2025, dropping Pro 10K from $60.50 to $16.50. The comparison numbers above reflect current rates after those changes.

bmail.ag is a separate product

bmail.ag is a completely separate company from AgentMail and solves a different problem.

• bmail.ag product: "Verifiably Private Email." End-to-end encrypted email secured by Intel SGX enclaves, OPAQUE authentication, and cryptographic key transparency. Includes Contacts, Calendar, and Drive, also E2E encrypted.
• bmail.ag pricing: free tier at $0; paid plans starting at approximately $4.95/month.
• bmail.ag domain registered March 11, 2026. No affiliation with AgentMail, Y Combinator, or AI agent email infrastructure.
• A separate blockchain variant ("bMail" on GitBook) requires token holdings rather than USD subscriptions; this may be legacy or a naming collision.

If you typed "bmail.ag pricing" looking for AI agent email API pricing, you want AgentMail (above) or one of the alternatives (below). If you typed it looking for end-to-end encrypted personal email, bmail.ag is the correct product but unrelated to anything in this article.

What cost-sensitive teams should look at

If you weighed AgentMail's pricing and concluded the per-email economics do not fit your workload, here are the realistic alternatives by use case:

• Pure outbound transactional at any volume: Amazon SES at $0.10 per 1,000 plus a dedicated IP at $24.95/month. Cheapest line item on the market. You build the inbox layer yourself.
• Outbound transactional with strong DX and broad SDK support: Resend at $20/month (50,000 emails included). 10 first-party SDKs, React Email pairing, broadcast SKU.
• Outbound transactional with deliverability depth: Postmark Pro at $16.50/month for 10,000 emails including inbound, or Mailgun Foundation at $35/month for 50,000 with Mailgun Optimize as a separately-priced add-on.
• Outbound + agent inboxes consolidated at low cost: Bavimail at $4/month Pro (10,000 emails, inbound and MCP included).

For the broader 6-product landscape, see AgentMail alternatives in 2026. The Bavimail vs AgentMail breakdown covers the head-to-head with pricing tables and feature coverage.

AgentMail's pricing is the right pick when you need many discrete agent inboxes with MCP and inbound included. It is the wrong pick when the workload is high-volume transactional send. The dollar amounts are public on both sides. The question is which job you are actually buying the email platform to do.