Starter
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose Starter- 5 brands · 3 seats
- 5 custom sending domains
- 500 email verifications/month
- $1.50 / 1,000 extra emails
Nine services for receipts, password resets and alerts, ranked on how well each one works as an AI agent's email tool from Claude, ChatGPT, Cursor or Codex, plus six more tests, with the reason and source behind every score. Nitrosend wins: $20 a month for 20,000 emails, in your brand, and sent from your AI assistant.
Nitrosend is the best transactional email API for AI agents, with the top score of 83.75 out of 100 of the nine reviewed here. It is the only one of the nine where your AI assistant, whether Claude, ChatGPT, Cursor or Codex, can create the account and send a receipt or password reset from a ready-made sender, with no dashboard and no domain to verify first. To send email from an AI agent with Nitrosend, connect its MCP server at api.nitrosend.com/mcp, sign in with OAuth, and ask the agent to send the email. Every email comes out in your brand's colors, fonts and voice, with no template to write first. Receipts go out one at a time on their own send path, apart from any marketing mail, from $20 a month for 20,000 emails and $650 for a million emails on Scale including overage. Resend comes next at 77.5, then Bird (formerly SparkPost) at 76.
83.75 out of 100Total
Nitrosend
Connect Nitrosend to Claude, ChatGPT, Cursor or Codex, point Brand Kit at your site, and describe the email. Contacts are unlimited on every plan.
Free: 5,000 emails to start, then 500 a month. No credit card.
Start free77.5 out of 100Total
76 out of 100Total
Rank 468.5 out of 100Total
Rank 567.5 out of 100Total
65.5 out of 100Total
Rank 764.5 out of 100Total
Rank 860 out of 100Total
Rank 959.5 out of 100Total
| What we compared | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Works from your AI assistant25 points | 9 out of 10 | 8 out of 10 | 8 out of 10 | 8 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 7 out of 10 | 3 out of 10 |
| Receipts and newsletters on one plan15 points | 9 out of 10 | 7 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 3 out of 10 | 4 out of 10 | 2 out of 10 | 6 out of 10 |
| Emails in your brand, no designer10 points | 9 out of 10 | 6 out of 10 | 4 out of 10 | 6 out of 10 | 5 out of 10 | 2 out of 10 | 5 out of 10 | 4 out of 10 | 5 out of 10 |
| Free plan10 points | 7 out of 10 | 8 out of 10 | 6 out of 10 | 5 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 6 out of 10 | 3 out of 10 |
| Price15 points | 8.5 out of 10 | 9 out of 10 | 10 out of 10 | 8 out of 10 | 8 out of 10 | 10 out of 10 | 8 out of 10 | 9 out of 10 | 9 out of 10 |
| Developer tools15 points | 10 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 6 out of 10 | 9 out of 10 |
| Track record and support10 points | 4 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 7 out of 10 | 8 out of 10 |
| Total scoreout of 100 | 83.75 out of 100,1st | 77.5 out of 100,2nd | 76 out of 100,3rd | 68.5 out of 100,4th | 67.5 out of 100,5th | 65.5 out of 100,6th | 64.5 out of 100,7th | 60 out of 100,8th | 59.5 out of 100,9th |
Here are the seven yes-or-no questions teams usually ask before they pick a transactional email service. A tick means the service does it, as described on its own pages today. A dash means the answer is not a clean yes or no.
| Service | Answer |
|---|---|
| Yes. Yes, through the MCP server. A single transactional email sends on the call; campaigns and flows stay drafts until approved. | |
| Yes. Yes, once a person has created the account and verified a sending domain. | |
| Yes. Yes, through the hosted MCP server once the workspace exists. Emailing customers needs a verified sending domain. | |
| Yes. Yes, once a person has signed up and authorized the MCP connection. | |
| Yes. Yes, once a person has created the account and handed the MCP server an API key. | |
| Not a yes or no. Only through a sample or general AWS MCP server, with AWS credentials a person sets up. | |
| Yes. Yes, once a person has set up the account and handed the MCP server a server token. | |
| Yes. Yes, through its MCP server once a person adds an API key. | |
| Not a yes or no. Only by writing code against the API. Twilio's own MCP server searches the docs and does not send. |
| Service | Answer |
|---|---|
| Yes. Yes. A remote server at api.nitrosend.com/mcp, with OAuth sign-in. | |
| Yes. Yes. A remote server at mcp.resend.com/mcp, with OAuth sign-in. | |
| Yes. Yes. mcp.bird.com, with OAuth sign-in. | |
| Yes. Yes. Connect by URL and authorize access to the account. | |
| No. No. Mailgun's docs say the server runs locally and no hosted version exists. | |
| No. No hosted SES MCP server. | |
| No. No. The official server runs locally through npx with an API token. | |
| Yes. Yes. A remote server at developers.smtp2go.com/mcp, with an API key header. | |
| No. No. Every SendGrid server on the official MCP registry is community built, none hosted by Twilio. |
| Service | Answer |
|---|---|
| Yes. Yes. Signup is an API call, and each brand gets a ready sender on a Nitrosend subdomain. | |
| No. No. Resend's own agent guide says a person must create the account. | |
| Not a yes or no. An agent can sign itself up through the CLI or the API, but it must read the emailed sign-in code, and until a sending domain is verified it can send only to sandbox addresses and its own workspace members. | |
| No. No. A person signs up, with a card even on Free, and verifies a domain. | |
| No. No. A person signs up and verifies a sending domain first. | |
| No. No. A person opens the AWS account, verifies a domain and requests production access. | |
| No. No. A person signs up and confirms a sender signature or domain first. | |
| No. No. A person signs up and verifies a sender domain first. | |
| No. No. A sender or a domain has to be verified before real sending. |
| Service | Answer |
|---|---|
| Yes. Yes, on every plan including Free. | |
| Not a yes or no. Broadcasts and automations are in the same account, on a separate marketing plan. | |
| Not a yes or no. Broadcasts share the email allowance. Email automations are in early access, with a separate run allowance. | |
| No. No. Bulk emailing, but no campaign builder or flows. | |
| No. No. Mailing lists and templates, but no campaign builder or flows. | |
| No. No. SES sends, and the campaigns and flows are yours to build. | |
| Not a yes or no. Broadcast streams handle bulk sends. There is no campaign builder or automation flows. | |
| No. No. Sending only. | |
| No. No. Marketing Campaigns is a separate plan, from $15 a month. |
| Service | Answer |
|---|---|
| Yes. Yes. 5,000 emails up front, then 500 a month. | |
| Yes. Yes. 3,000 emails a month, 100 a day. | |
| Yes. Yes. 1,000 emails a month, no time limit. | |
| Yes. Yes. 500 emails a month. | |
| Yes. Yes. 100 emails a day. | |
| No. No. Up to $200 in AWS credits for new customers. | |
| Yes. Yes. 100 emails a month on the Developer plan, with no expiry. | |
| Yes. Yes. 1,000 emails a month. | |
| No. No. 100 emails a day for 60 days, then a paid plan. |
| Service | Answer |
|---|---|
| Yes. Yes. Brand Kit scans your site, and AI Memory keeps house style. | |
| Not a yes or no. Its AI features list URL and brand analysis, which its docs do not describe yet. | |
| No. No. Templates and React Email, and you supply the design. | |
| No. No. Templates are built in its editors. | |
| No. No. Templates are built in its builder or in HTML. | |
| No. No. Templates are HTML you write. | |
| No. No. A template library you edit into your own brand. | |
| No. No. Templates are yours to build. | |
| No. No. Templates and a design editor, but you supply the design. |
| Service | Answer |
|---|---|
| Not a yes or no. An agent inbox on your own domain, enabled by request. | |
| Yes. Yes, on every plan. | |
| Yes. Yes. Inbound domains and relay webhooks. | |
| Yes. Yes, through inbound routing. | |
| Yes. Yes, through inbound routes. | |
| Yes. Yes. SES receives mail through receipt rules and Mail Manager. | |
| Yes. Yes, with inbound processing on Pro and Platform. | |
| No. No inbound email in its developer docs. | |
| Yes. Yes, with Inbound Parse. |
At a glance
9 services, the same 7 tests, 100 points in all. In order: Nitrosend 83.75, Resend 77.5, Bird 76, MailerSend 68.5, Mailgun 67.5, SES 65.5, Postmark 64.5, SMTP2GO 60, SendGrid 59.5. Nitrosend has the best score on Works from your AI assistant, Receipts and newsletters on one plan, Emails in your brand, no designer and Developer tools. Every price and feature was read on each company's own pages on September 26, 2026.
This page ranks services on transactional email alone, the receipts, password resets and alerts an app or an agent fires one at a time. If the same agent also sends your newsletters and automated flows, the ranking of the best email API for receipts and newsletters together compares the services that run both jobs from one API. Nitrosend does not win every test here. Read these before you choose it.
Transactional volume grows with your users, not with your marketing calendar, so the price that matters is the one a year out. Eight of these services sell plans by emails sent. Amazon SES is metered, at $0.10 per 1,000 a la carte or $0.16 per 1,000 on the Essentials plan that new accounts default to from July 21, 2026.
| Service | 20,000 emails a month | 1,000,000 emails a month |
|---|---|---|
| Nitrosend (pricing page) | $20Pro, contacts unlimited | $650Scale, contacts unlimited, including overage |
| Resend (pricing page) | $20Pro, which covers 50,000 | $650Scale |
| Bird (pricing page) | $15Startup, which covers 50,000 | $530Growth |
| MailerSend (pricing page) | $35Starter, the first plan with 50 webhooks and 250 templates. Hobby with overage is $29.50 but has 1 webhook and 10 templates | $600Starter |
| Mailgun (pricing page) | $33Basic, 10,000 included and $1.80 per 1,000 after | $700Scale |
| SES (pricing page) | $3.20Lowest. Essentials, the default for a new account, or $2 a la carte. Charged per email | $160Lowest. Essentials, the default for a new account, or $100 a la carte. Charged per email |
| Postmark (pricing page) | $29.50Pro, 10,000 included and $1.30 per 1,000 after. Basic is $33 | $775Basic, the 1,500,000 plan. Pro is $852.50 |
| SMTP2GO (pricing page) | $27Starter, 10,000 included and $1.20 per 1,000 after | $520Professional |
| SendGrid (pricing page) | $19.95Essentials, which covers 50,000 | $799Pro, the 1,500,000 plan. The 700,000 plan is $499 |
At 20,000 emails a month, Nitrosend is $20, the same as Resend. Three cost less: Amazon SES at $3.20, Bird at $15 and SendGrid at $19.95. SMTP2GO is $27, Postmark $29.50, Mailgun $33 and MailerSend $35.
At a million emails a month, Nitrosend is $650. SMTP2GO is $520, Bird $530, MailerSend $600, Resend $650, Mailgun $700, Postmark $775 and SendGrid $799. Amazon SES is $160, with the templates and reporting yours to build.
What the $20 buys is the other half. The same plan and the same key carry newsletters, segments and automated flows on their own send path, so the welcome series that follows a signup does not need a second vendor. If you would otherwise buy a second product for that, add the two bills together before you compare.
Every service gets a score out of 10 on the same seven tests. Each test is worth a set number of points, 100 in all. Working from your AI assistant is worth the most, 25 points, because that is where email is heading. Price, developer tools and track record, where the specialist transactional services are strongest, share 40 points, so a service that is better there gets full credit for it.
Each test is a question with one answer per service, checked against the service's own pages on September 26, 2026. A 10 means it does the job fully on its normal plans. A 5 means it does part of it, or only on a higher plan or in a second product.
Works from your AI assistant, 25 points. Can an agent inside Claude, ChatGPT, Cursor or Codex go from nothing to a delivered transactional email, and then read back what happened to it, with no person opening the web app along the way? Scored on the first-party MCP server and what its tools cover, a CLI that works in a non-interactive runner, account and sender setup over the API, and listings in the chat apps people already work in. Scored on one written rule for every vendor: a first-party server the vendor runs and that can send counts fully; a third-party wrapper (Zapier, Composio, Kanopi, community servers) counts for less; a server that only drafts or reads counts for less than one that sends.
Receipts and newsletters on one plan, 15 points. Can receipts and password resets, and the newsletters and automated flows that follow them, go out from one account, on one bill, through one API, with the two streams kept apart?
Emails in your brand, no designer, 10 points. Does the product produce the receipt, reset and welcome emails in your brand's own logo, colors, fonts and voice, or does a developer have to write or buy the HTML template first?
Free plan, 10 points. How far can a developer get on the free plan before paying: the monthly volume, the daily ceiling, any one-off starter allowance, and whether the plan is perpetual or a trial that ends.
Price, 15 points. What does sending cost at 20,000 emails a month, where most teams start, and at 1,000,000, where a busy product ends up? Scored on list prices in US dollars, paid monthly, at the cheapest plan that covers the volume. Every ranking on this site uses the same fixed scale. At 20,000 emails, $20 or less scores 10, then $25 scores 9, $32 scores 8, $40 scores 7, $50 scores 6, $70 scores 5, $100 scores 4 and $140 scores 3. At 1,000,000, $500 or less scores 10, then $625, $800, $1,000, $1,250, $1,750, $2,500 and $3,500 step down the same way. Anything dearer, or a price given only by quote, scores 2. The score is the average of the two.
Developer tools, 15 points. How complete is what a developer builds on: a REST API with an OpenAPI spec, official SDKs across languages, a CLI, an SMTP relay, documented delivery-event webhooks, idempotent sends, a test or sandbox mode, inbound email handling, and how deep the reference docs go?
Track record and support, 10 points. How long has it run transactional sending at scale, which deliverability controls can you own (dedicated IPs, suppression, separate streams, a published uptime SLA), and what support comes with the plan?
One thing is not scored: inbox placement. No two of these services publish a comparable deliverability number, so a score there would be a guess dressed up as a measurement. Postmark publishes its own time to inbox, and it is the service to read closely if speed to the inbox is the whole job.
A transactional email API sends one message to one person because of something they did: a password reset, a receipt, a one-time code, an order confirmation, a system alert. It is kept apart from marketing email because the two want opposite things. Transactional mail has to arrive in seconds and may reach people who have unsubscribed from marketing. Marketing mail is batched, segmented and sent only to people who agreed to it. Transactional email, defined has the longer version, and transactional email compared with marketing email covers where the line sits.
The API has three jobs. It accepts the message fast and gives you an identifier. It gets the message past the receiving server's checks, which is mostly authentication and reputation. And it tells you what happened, through logs you can search when a customer says the reset never came. The email authentication records are what the second job rests on, and what email deliverability is covers the rest.
The third job is where a support ticket gets answered, and accepted is not delivered. In Nitrosend's delivery events, email.sent means the provider took the message and email.delivered means the recipient's mail server did. Every event carries the idempotency key and tags the message was sent with, so "the reset never came" traces back to one send by your own order or user id. The events are signed in the Standard Webhooks format, so any of its libraries can verify them, and they cover single transactional messages, not campaigns or flows.
Those three jobs are becoming the floor, not the product. George Hartley, Nitrosend's co-founder, said on SaaS Stories in September 2026: "in the future future, there's going to be a bunch of kind of dumb email pipes that these agents will just sit on top of. But we do think we can kind of be smarter than that if we look at actually how can people improve based on all of the volume that's going through." When you compare the services below, the delivery basics should be table stakes; the difference worth paying for is what the provider tells you, or your agent, about what to fix.
Transactional emails are the most underrated messages in the inbox. They are the emails people open because they asked for them, and most companies treat them as plumbing.
Treating them as plumbing wastes the space. A receipt or a welcome email is a brand moment, because it is the one message you can be sure the customer opens. This is why the tests on this page give 10 points to emails that come out in your brand without a designer. Transactional email best practices has the checklist.
The engineering side is discipline. A receipt with a promotion bolted on can stop being transactional. Under the US CAN-SPAM Act, the FTC judges an email by its primary purpose, and one whose primary purpose is promotion needs an unsubscribe link like any marketing email. Keep the streams apart, keep the receipt a receipt, and test the message you are about to send rather than a copy of it.
No. Put them on separate subdomains, on day one, before you have a reputation to protect. If notifications.yourapp.com carries password resets and mail.yourapp.com carries campaigns, a campaign that draws complaints cannot drag the resets into spam with it. Providers keep the two apart in different ways: Postmark with message streams on separate IPs, SendGrid with IP pools, Mailgun with dedicated IP pools, and Amazon SES with tenants that separate identities, configuration and reputation. Nitrosend sends a receipt through a single-message call that goes out at once, while campaigns and flows wait as drafts until someone approves them, and its Pro plan covers three customer sending domains, enough for both subdomains. Any of those works, as long as the split is there before the first big send.
Nitrosend, with the top score in this review, 83.75 out of 100. It is the only service here an AI assistant can set up and send from with no dashboard and no domain to verify first. A receipt goes out on one call, while newsletters and flows wait as drafts until someone approves them. It writes receipts and resets in your brand with no template to build, and it costs $20 a month for 20,000 emails. Resend is second at 77.5 and Bird third at 76. Pick Postmark if track record comes first, and Amazon SES if unit cost at volume decides it.
Nitrosend. It scores 9 out of 10 on working from your AI assistant, the test worth the most points, because its MCP server, account signup over the API and ready-made sender let an agent in Claude, ChatGPT, Cursor or Codex fire a receipt with nobody opening a dashboard. Resend scores 8 because, by its own AI onboarding docs, a human must create the account and a domain must be verified before the agent can send. Bird scores 8 because, although an agent can create the account, a sending domain has to be verified first. MailerSend scores 8, SMTP2GO and Amazon SES 7 (through AWS's own managed MCP server), Postmark and Mailgun 6, and SendGrid 3, because Twilio's MCP server has two tools that search and retrieve API documentation and none that sends. Best email API for AI agents ranks the field on that job alone.
In Claude, enable the official Nitrosend connector from the Claude directory and sign in. In Claude Code, run claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp and complete the OAuth sign-in. Then ask Claude to send the receipt. It uses the nitro_send_message tool, which sends one transactional email to a single recipient immediately. Give each receipt a stable idempotency key, such as the order number, and a retry of the same request cannot deliver it twice. The Nitrosend MCP docs cover ChatGPT, Cursor and Codex as well.
Accepted in well under a second and delivered within seconds. If password resets routinely take minutes, look at queueing and sender reputation before you blame the provider, and check the email authentication records first. A reset also has a shelf life. OWASP's password reset guidance says reset tokens should be single use and expire after an appropriate period, so a reset delivered hours late is a dead link. When Nitrosend refuses a send for lack of capacity, its docs tell API callers to follow the returned retry time rather than retrying in a loop or treating the refusal as delivered.
A separate path for transactional mail, a dedicated IP once your volume can keep it warm, and logs you can search when a customer says the email never came. Postmark has message streams, and its pricing page lists managed dedicated IPs and 45-day retention. Amazon SES lists managed dedicated IPs, Virtual Deliverability Manager and tenants. Mailgun has dedicated IP pools and IP warm-up, and Bird sells dedicated IPs from Growth. Nitrosend sends receipts through its single-message path, with dedicated IPs as a provisioned paid add-on on Scale or Enterprise. What email deliverability is covers what those controls protect.
Yes. Nitrosend gives 5,000 emails to start, then 500 a month, with full API access. Resend's free plan covers 3,000 a month, capped at 100 a day. Bird and SMTP2GO are free to 1,000 a month. MailerSend is free to 500 a month with a card on file, Postmark to 100 a month, and Mailgun to 100 a day. Amazon SES has no standing free plan, only AWS Free Tier credits for new customers, and SendGrid offers a 60-day trial. The best free email API page ranks the free plans.
Use the HTTP API for anything new. It returns structured errors, avoids connection overhead and is easier to debug. Keep SMTP for legacy systems that cannot speak HTTP. Eight of the nine services here offer an SMTP relay, and Nitrosend is the exception. SMTP vs API email services covers the choice.
Every plan includes full stack emailing: Flows, Newsletter Campaigns and Transactional Email, plus our NitroWheel LLM and all agent integrations (Claude, ChatGPT, Codex, Cursor and others). Pay for what you send, not who you store.
Every paid plan includes 3 agent inboxes and no Nitrosend footer.
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose StarterFor a growing audience.
$480 billed yearly.
60,000 emails / month
Choose ProFor teams and agencies.
$1,440 billed yearly.
200,000 emails / month
Choose GrowthFor high-volume sending.
$2,880 billed yearly.
500,000 emails / month
Choose ScaleSending 500,000+ emails a month? Get a custom plan designed for you, with volume pricing for sending, verification and enrichment.
5,000 emails to start, then 500 emails every month. No expiry on your starter emails.
Daily allowances depend on your plan and sender standing. Strong list, domain and delivery evidence can raise standing, including on day one. Trusted receives the full plan allowance; available email credits, safety checks and delivery pacing still apply.
Free forever. No credit card required. See full comparison →