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 sending APIs ranked on how well each one works as an AI agent's email tool, from Claude, ChatGPT, Cursor or Codex, on the same seven tests with the reason and source behind every score. Nitrosend wins: $20 a month for 20,000 emails, and the only one an agent can sign up to and send from with no dashboard.
Nitrosend is the best email sending API for teams that run email from AI, with the top score of the eight reviewed here, 83.75 out of 100. It scores 9 out of 10 on working from your AI assistant, the heaviest test, and it is the only one of the eight that Claude, ChatGPT, Cursor or Codex can sign up to and send from without anyone opening a dashboard. To send email from an AI agent with Nitrosend, connect the agent to its MCP server at api.nitrosend.com/mcp and sign in with OAuth. A single transactional email then goes out in one call, and a campaign or flow stays a draft until it is approved. Every send takes an Idempotency-Key, so a retry after a timeout cannot become a second email, and your receipts and newsletters go out from one account on one plan. 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 Brevo at 70.
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
Rank 370 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 859.5 out of 100Total
| What we compared | ||||||||
|---|---|---|---|---|---|---|---|---|
| Works from your AI assistant25 points | 9 out of 10 | 8 out of 10 | 5 out of 10 | 8 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 3 out of 10 |
| Receipts and newsletters on one plan15 points | 9 out of 10 | 7 out of 10 | 8 out of 10 | 4 out of 10 | 4 out of 10 | 3 out of 10 | 4 out of 10 | 6 out of 10 |
| Emails in your brand, no designer10 points | 9 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 5 out of 10 | 2 out of 10 | 5 out of 10 | 5 out of 10 |
| Free plan10 points | 7 out of 10 | 8 out of 10 | 9 out of 10 | 5 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 3 out of 10 |
| Price15 points | 8.5 out of 10 | 9 out of 10 | 6 out of 10 | 8 out of 10 | 8 out of 10 | 10 out of 10 | 8 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 | 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 | 8 out of 10 |
| Total scoreout of 100 | 83.75 out of 100,1st | 77.5 out of 100,2nd | 70 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 | 59.5 out of 100,8th |
Here are the seven yes-or-no questions developers usually ask before they pick a sending API. 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. | |
| Not a yes or no. The hosted MCP server creates and manages campaigns, but no tool for sending a transactional email is documented. | |
| 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. | |
| 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.brevo.com, signed in with a token a person generates in the web app. | |
| 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. | |
| 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. | |
| No. No. A person creates the account and the MCP token, and Brevo approves the account before it sends. | |
| 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 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. | |
| Yes. Yes. Transactional is on every plan and automation runs from Free up to 2,000 contacts and from Standard without a limit. | |
| 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. 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. 300 emails a day with 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. | |
| 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. | |
| Yes. Yes. The brand library fetches logo, colors, fonts and links from a URL, not tone of voice. | |
| 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 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 parsing posts replies to your webhook as JSON. | |
| 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. | |
| 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, Brevo 70, MailerSend 68.5, Mailgun 67.5, SES 65.5, Postmark 64.5, 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.
Nitrosend does not win every test. Read these before you choose it.
Every service here charges by emails sent except Amazon SES, which 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.
| 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 |
| Brevo (pricing page) | $69Standard, the first plan with automation. Starter is $32 without it | $999Professional. Standard stops at 500,000 emails |
| 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 |
| 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 and a nickel more than SendGrid at $19.95. Postmark is $29.50, Mailgun $33, MailerSend $35 and Brevo $69 on Standard, the plan priced here because it is the first with automated emails, the fair comparison with Nitrosend's $20 (Starter is $32 without them).
At a million emails a month, Nitrosend is $650. MailerSend is $600, Resend $650, Mailgun $700, Postmark $775, SendGrid $799 and Brevo $999. With Amazon SES the templates, unsubscribe handling and reporting are yours to build.
A million a month is also where the ramp matters more than the price. Whichever service you pick, the first month at that volume is held back by the ramp described below, so plan the move before the bill forces it. Nitrosend's $650 also carries campaigns and flows on the same key, so if you would otherwise pay for a second product, 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. Coding assistants now add a hosted tool server with one command and a browser sign-in, as OpenAI's Codex guide to MCP shows, so the first thing a new sending API meets is often an assistant asked to wire it up. The test is whether that assistant can get from sign-up to a delivered email without handing the job back to a person. Price, developer tools and track record, where the specialist sending 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?
Two things are not scored. Inbox placement, because no two of these services publish a comparable deliverability number. And raw throughput, because none of them publishes a comparable ceiling for a new account, and every one of them holds a new sender to a ramp.
An email sending API is the part of a provider that takes your message and gets the receiving mail server to accept it: queueing, throughput, retries, bounce and complaint handling, and the limits that decide how fast you may go. A 200 response means the provider has taken the message. Everything that decides whether it reaches an inbox happens after that.
email.failed webhook fires only once a send has failed for good, never while it is still being retried, so nothing gets resent while the first copy may still arrive.Idempotency-Key header on a send for exactly this, and a retry with the same key does not send again. It is the same pattern Stripe documents for retrying a payment safely.Every provider limits how fast a new sender can go, and it is the most common frustration in this category. It is also correct. Mailbox providers judge you on your sending pattern, and Google's sender guidelines warn that suddenly doubling your volume can get you rate limited or cost you reputation.
Warm up gradually and raise volume with each send, especially with a large list. If you are moving providers, do not assume your old reputation comes with you, because reputation belongs to the sending domain and IP, not to you. How to warm up an email domain covers the ramp, and IP warming covers dedicated IPs. Google Postmaster Tools is the free source of truth for Gmail while you do it.
Nitrosend meters sending capacity separately from email credits. On the Free plan it is 100 recipients per rolling 24 hours, rising as the account builds a delivery record, so a large first import is held to the same ramp as everywhere else.
One kind of mail should not go through a bulk sending API at all. George Hartley, Nitrosend's co-founder, put it plainly on SaaS Stories in September 2026: "outbound actually sort of has to run from email addresses, right? You can't run outbound through a bulk system because that's immediately going to cook everything like Gmail will just cut you off." His answer for agents that do outreach is a mailbox of their own: "agents need their own email addresses." He described the same turn on The Breakout CEO in August, once agents could sign up and send on their own: "Oh, actually they need an inbox as well." So keep one-to-one outreach on individual mailboxes, and use a sending API for the receipts, notifications and campaigns your recipients asked for.
Nitrosend, with the top score in this review, 83.75 out of 100. It is the only service here an AI assistant can sign up to and send from without anyone opening a dashboard, while a campaign or flow still waits as a draft until it is approved. Sends take an idempotency key so retries cannot double up, and campaigns and flows run on the same plan from $20 a month. Pick Amazon SES for raw throughput at the lowest cost, and Postmark or Mailgun for the longest record of sending at scale.
Because your sending domain and IP have not built a reputation yet. Limits rise as you send steadily to people who engage. It is a reputation system, not a billing tactic, and every service on this page has one.
A hard bounce should put the address on a suppression list at once, for the whole account. A soft bounce is retried for a window before it is treated as a failure. Every service here does this automatically. Email bounce rate covers the thresholds.
The API, for anything new. It returns structured errors, tells you at once whether the message was accepted and gives you an identifier to track it. Keep SMTP for legacy systems that speak nothing else. Seven of the eight services here offer an SMTP relay, and Nitrosend sends through its API, CLI and MCP server only. SMTP vs API email services covers the choice.
Validate the list first, then ramp up gradually from a warmed domain. Importing a large unvalidated list and sending to all of it is the fastest way to hit a bounce threshold and stall. Best email validation API ranks the services that clean a list first.
Nitrosend, which scores 9 out of 10 on working from your AI assistant, ahead of Resend and MailerSend at 8. Nitrosend, Resend, MailerSend and Brevo host MCP servers an assistant can connect to, and Postmark and Mailgun publish ones you run yourself. Of the eight here, only Nitrosend lets the agent create the account and get a ready sender without a person verifying a domain first. Best email API ranks the wider field.
In Claude Code, run claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp and finish the sign-in. In Codex, run codex mcp add nitrosend --url https://api.nitrosend.com/mcp, then codex mcp login nitrosend. Claude.ai, Claude Desktop and ChatGPT connect through their own connector and app directories, with no key to paste. Then ask for the email. A single transactional email goes out at once with an idempotency key, and a campaign or flow is saved as a draft until it is approved. Connecting Claude Code covers the first setup.
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 →