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
Eight services that send your app's email, ranked on how well each one works as an AI agent's email tool, from Claude, ChatGPT, Cursor or Codex. Same seven tests, with the reason and source behind every score. Nitrosend wins: $20 a month for 20,000 emails, and built to run from your AI assistant.
Nitrosend is the best email API service for teams that run email from an AI agent, with the top score of 83.75 out of 100 across the eight reviewed here. It is the only one of the eight here your AI assistant, whether Claude, ChatGPT, Cursor or Codex, can sign up to and send from without anyone opening a dashboard. To set it up, add Nitrosend's MCP server, https://api.nitrosend.com/mcp, to Claude, Cursor or Codex and sign in with OAuth, or install the Nitrosend app in ChatGPT. Campaigns and flows then stay drafts until approved, and a single transactional email sends on the call. It writes every email in your brand's colors, fonts and voice, and your receipts and newsletters go out on one plan and one bill. It costs $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 467.5 out of 100Total
65.5 out of 100Total
Rank 664.5 out of 100Total
Rank 760 out of 100Total
Rank 859.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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 67.5 out of 100,4th | 65.5 out of 100,5th | 64.5 out of 100,6th | 60 out of 100,7th | 59.5 out of 100,8th |
Here are the seven yes-or-no questions developers usually ask before they pick one of these services. 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 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. | |
| 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 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. 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. 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 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 |
|---|---|
| Yes. Yes. An agent inbox on your own domain posts incoming mail to your webhook. | |
| Yes. Yes, on every plan. | |
| Yes. Yes. Inbound domains and relay webhooks. | |
| 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
8 services, the same 7 tests, 100 points in all. In order: Nitrosend 83.75, Resend 77.5, Bird 76, 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 25, 2026.
Nitrosend does not win every test. Read these before you choose it.
Every service here charges by emails sent, except two. 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 since July 21, 2026. SendGrid bills its Email API on a send-volume slider and Marketing Campaigns on stored contacts, so if you want both, you pay twice, on two different units.
| Service | 20,000 emails a month | 1,000,000 emails a month |
|---|---|---|
| Nitrosend (pricing page) | $20Starter, 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 |
| 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, where most teams start, Nitrosend is $20. That is the same as Resend, and within a few dollars of Bird at $15 and SendGrid at $19.95. Postmark, Mailgun and SMTP2GO charge for every email past 10,000, which puts them at $27 to $33.
At a million emails a month, Nitrosend is $650. SMTP2GO is $520, Bird $530, Resend $650, Mailgun $700, Postmark $775 and SendGrid $799. With Amazon SES the templates, unsubscribe handling and reporting are yours to build. Once your list is large, what email marketing really costs has the wider math.
The bigger difference is what the $20 buys. Nitrosend's own developer page puts it plainly: most email APIs stop at "send a message", and Nitrosend provides the entire stack through the same key, lists, segments, automated flows, brands, templates and deliverability, alongside a single-call transactional send. If you would otherwise buy a second product for campaigns, 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 older 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 25, 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.
Working from your AI assistant carries 25 points because that is where sending is moving. The Model Context Protocol is now the common way to plug a tool into an assistant, supported by Claude, ChatGPT, Cursor and Visual Studio Code among others, according to the protocol's own documentation. Having an MCP server is not the same as an agent being able to send through it. Twilio's MCP server is read-only: it searches API documentation and does not execute API calls. So the test asks whether an agent can do the whole job, from an empty account to a delivered email and a report on what happened. The older services were built around a dashboard and a large feature set, and rebuilding all of that to run from a chat window is a large job, which is why most of them score lower here. Their uptime is not in question.
Receipts and newsletters on one plan is worth 15 points for a less obvious reason: the two follow different rules. Gmail requires one-click unsubscribe on marketing and promotional mail and excludes transactional messages such as password resets, according to Google's sender guidelines FAQ. Postmark keeps transactional and broadcast traffic on separate streams and IP ranges, which it says follows inbox providers' advice on separating reputation (Postmark's Message Streams page). One account therefore has to keep the two apart underneath while letting one assistant see both. When receipts and campaigns run on two providers, whoever owns each one rarely sees the other's email. On one account, the assistant can report on everything going out.
Three things: delivery, developer tools, and a way for your AI assistant to run both. Vendors differ far more on the last two.
Outbound delivery. Transactional streams carry one-to-one messages set off by something a user did: receipts, password resets, invitations, new accounts. Marketing streams carry one-to-many sends. Providers keep the two apart to protect reputation. A newsletter at Gmail's 0.3% spam-rate limit, set in Google's email sender guidelines, should not be able to drag a password reset into the spam folder, and a provider that pools both on one reputation lets it. Transactional email compared with marketing email covers the split.
Developer tools. This is where most of the choice gets made. Nitrosend scores 10 here: a REST API with an OpenAPI spec, a typed TypeScript SDK, a CLI, an MCP server, signed event webhooks, idempotent sends and test sends.
MCP.Working from your AI assistant. The newest part, and the one this review gives the most points. An agent needs an MCP server whose tools cover the whole job, a sender it can use before anyone edits DNS, a test send, an approval step and a way to read back what happened. Nitrosend covers each one: its MCP tools draft, test, approve and send, a shared sandbox sender lets the first test go out before a domain is verified, Brand Kit keeps every draft in your colors, fonts and voice, and the agent reads the analytics back through the same server.
George Hartley, Nitrosend's co-founder, gives that last part the most weight because of what he sees in Nitrosend's own usage. On SaaS Stories in September 2026 he said: "94% of our usage is via the MCP from an agent doing stuff." He had already said where it leads on X in July: "Soon there'll be 100 billion AI agents. Every one of them needs email."
One risk is specific to agents. An assistant whose tool call times out may simply try again, and a repeated POST can send the same receipt twice. The IETF draft for the Idempotency-Key header exists to make POST requests like this fault-tolerant. Nitrosend accepts that header on sends: a retry with the same key and the same message returns the original message rather than sending a second one, and the same key with a different message is refused. Check that any service you let an agent send through does the same.
Both reach the same infrastructure. What differs is the protocol in front of it.
An email API speaks HTTP. It is faster, copes better with bursts and makes attachments simpler. The response tells you at once whether the message was accepted and gives you an identifier to track it, and errors come back structured. If you are writing the code today, use the API.
An SMTP relay speaks the mail protocol. It is slower, chattier and tells you far less, but it is universal. A legacy application, a printer, a CRM or a WordPress plugin will speak SMTP and nothing else, and rewriting them is not worth it. Seven of the eight services here offer both. Nitrosend is the exception. It sends through the API, the CLI and the MCP server, because it was designed for an agent or an application to call, not for a printer. The SMTP relay page has the setup for the others, and webhook versus API covers the event side.
Yes, and it is usually the lower-risk move. Nitrosend supports bring-your-own sending keys for SendGrid, Mailgun, Postmark, Resend and Amazon SES. Point it at the key you already have. You keep the same sending reputation, the same IPs and the same warm-up history, while your contact lists, segments, flows and reporting move over. Nothing on the transactional path changes on day one. That is deliberate, because changing the sending provider and the campaign tools in the same week is how migrations go wrong. The bring-your-own sending keys page has the mechanics, and it is why this review can be specific about where those five beat Nitrosend.
Swapping the API takes an afternoon. The reputation takes weeks.
An email API service is infrastructure your application calls over HTTP to send email, so you do not run your own mail server. You POST a message with a recipient, a subject and a body. The service handles queuing, authentication, retries and reputation, then sends delivery, bounce, open, click and complaint events back to you over webhooks. It sits behind password resets, receipts, notifications and, on some providers, marketing campaigns too.
Nitrosend, with the top score in this review, 83.75 out of 100, and the heaviest test here is how well a service works from your AI assistant. It is the only service here where an AI assistant can create the account, get a ready sender and make the first send without a person verifying a domain, and lists, segments and flows come on the same key, from $20 a month. Pick Resend if you are wiring transactional email into application code and want SDKs in many languages and an SMTP relay. Amazon SES suits a team already in AWS that is happy to build the missing pieces.
Several, at different sizes. Nitrosend gives 5,000 emails to start, then 500 a month, with full API, MCP and CLI access on every plan. Resend is free to 3,000 emails a month, capped at 100 a day. Mailgun is free to 100 emails a day. Bird and SMTP2GO are both free to 1,000 emails a month. Postmark's Developer plan is 100 emails a month with no expiry. SendGrid's free tier ended on July 26, 2025, replaced by 60 days at 100 emails a day, and Amazon SES offers new customers up to $200 in AWS credits rather than a free plan.
Postmark, Mailgun, SendGrid, Resend, Bird and Amazon SES all accept inbound mail and hand it to your application as structured data over a webhook. Nitrosend's Agent Inbox does the same for the addresses you set up as inboxes, and exposes each thread over REST and MCP so your code or an agent can read and reply. Mail it quarantines as spam, a virus or a blocked sender is not posted. If your application receives mail at addresses you cannot set up in advance, use one of the others for that part.
Yes, and it is now a normal reason to choose one provider over another. Nitrosend, Resend, Bird, SMTP2GO, Postmark and Mailgun all publish first-party MCP servers, and AWS runs a managed one that can send through Amazon SES, though only Nitrosend, Resend, Bird, SMTP2GO and AWS host theirs, and only Nitrosend, of the eight here, lets the agent create the account and get a ready sender without a person verifying a domain first. Nitrosend's server exposes tools for sending, contacts, segments, flows and reporting, with an approval step before a campaign or flow goes out. Email MCP explains what the protocol does.
Connect Nitrosend once, then ask. In Claude Code, run claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp, then /mcp to sign in with OAuth. In Claude Desktop or Claude.ai, turn on the official Nitrosend connector under Settings, Connectors. Then ask Claude for the email. Brand Kit reads your site for logo, colors, fonts and voice, Claude drafts the message and offers a test send, and a campaign or flow stays a draft until approved. A single receipt or password reset uses the immediate send tool instead. The same server works in Cursor and Codex, and ChatGPT connects through the Nitrosend app.
Bird, formerly MessageBird, acquired SparkPost in 2021 and has retired the name. sparkpost.com now redirects to bird.com, where the email product is sold as Bird Email on the same infrastructure, with the SparkPost developer documentation still served at developers.sparkpost.com. This page scores it as Bird.
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 email pricing and capacity that fits your business.
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 →