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 email APIs ranked on how well an AI agent in Claude, ChatGPT, Cursor or Codex can set up, send and check email through each one, plus the SDK and SMTP questions developers ask first. Nitrosend wins: $20 a month for 20,000 emails, and the only one an agent can sign up to on its own.
Nitrosend is the best email API for developers who run email from AI agents, with the top score of 83.75 out of 100 across the eight reviewed here. It is the only one your AI assistant, whether Claude, ChatGPT, Cursor or Codex, can sign up to and send from without anyone opening a dashboard, and it scores 9 out of 10 on working from your AI assistant, the heaviest test on the page. To send email from an AI agent with Nitrosend, add its MCP server at api.nitrosend.com/mcp in Claude, ChatGPT, Cursor or Codex and sign in once with OAuth; a script or headless agent can instead sign up, mint a key and send over plain HTTP. Its typed Node SDK, its CLI and its MCP server all reach the whole platform, so your receipts, newsletters and automated flows run on one key and one bill. It costs $20 a month for 20,000 emails. Resend comes next at 77.5, then Loops at 73.
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
73 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 | 8 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 | 9 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 | 5 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 | 7 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 | 8 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 | 7 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 | 5 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 | 73 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 nine yes-or-no questions developers usually ask before they pick an email 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. | |
| Yes. Yes, a published transactional email, once a person has signed in and connected the MCP server. | |
| 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.loops.so, with 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. | |
| 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 signs in to Loops in a browser. | |
| 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. Campaigns, workflows and transactional on every plan. | |
| 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. 4,000 sends in any 30 days, with a Loops footer. | |
| 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. | |
| No. No. Themes are set up by hand. | |
| 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. | |
| No. No inbound email in the documentation. | |
| 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. |
| Service | Answer |
|---|---|
| No. No. Node and TypeScript only. Other languages call the REST API. | |
| Yes. Yes. Official SDKs across languages, listed in its docs. | |
| No. No. JavaScript, Go, PHP and Ruby, four in all. | |
| Yes. Yes. Seven SDKs. | |
| Yes. Yes. Official SDKs in six languages. | |
| Yes. Yes. The AWS SDKs cover every major language. | |
| Yes. Yes. Official libraries for Node.js and TypeScript, Python, Ruby, .NET, Java and PHP. Go is community-only. | |
| Yes. Yes. SDKs in seven languages. |
| Service | Answer |
|---|---|
| No. No. Sending is through the API, the CLI and the MCP server. | |
| Yes. Yes. An SMTP relay on every plan. | |
| Yes. Yes. An SMTP service, with guides for Rails, Laravel and Supabase. | |
| Yes. Yes. An SMTP relay. | |
| Yes. Yes. An SMTP relay. | |
| Yes. Yes. An SMTP interface. | |
| Yes. Yes. SMTP alongside the API. | |
| Yes. Yes. An SMTP relay. |
At a glance
8 services, the same 7 tests, 100 points in all. In order: Nitrosend 83.75, Resend 77.5, Loops 73, 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. Two of the questions above, SDK languages and an SMTP relay, go against it. Read these before you choose it.
Most services here charge by emails sent. Amazon SES is metered per email. Loops charges by subscribed contacts, with sends unlimited on every paid plan, so a transactional-only sender pays for its smallest paid plan whatever the volume.
| 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 |
| Loops (pricing page) | $49The 1,001 to 5,000 contacts plan, sends unlimited | $49Lowest. The same plan. Transactional sends are unlimited on every paid plan |
| 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 | $160Essentials, 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, where most teams start, Nitrosend is $20. Amazon SES is $3.20, SendGrid $19.95, Resend $20, Postmark $29.50, Mailgun $33, MailerSend $35 and Loops $49.
At a million emails a month, Nitrosend is $650. MailerSend is $600, Resend $650, Mailgun $700, Postmark $775 and SendGrid $799. Loops is $49 for transactional email, though its price climbs with every subscribed contact once you send newsletters too. Amazon SES is $160, and the product layer is yours to build.
The $20 buys more than sending. Nitrosend's developer page says 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 used on the email API service rankings. 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 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.
Email is slower to first value than almost any other developer tool, and the cause is the setup, not the code. Before a real message goes out, most services ask for an API key, DNS records, a wait for them to propagate, a verified domain and often a review queue. A payments API such as Stripe hands you a sandbox with test keys and test cards whose charges move no money, so the first call works before anything is live. Email test modes let you write the code too, but real delivery still waits on the domain, which is why the domain step, not the code, is where most first sends stall.
Nitrosend removes the DNS wait from the first send. An agent or a script can create the account with POST /v1/signup, mint a key, activate a reserved sender on a subdomain Nitrosend already owns and has already verified, then send with POST /v1/my/messages and an Idempotency-Key header. Your own domain comes later, when you want your own reputation. The quickstart walks through it, and the CLI does the same from a terminal.
Every other service here needs a person to sign up and verify a domain or a sender address before real mail leaves. Most offer a test mode, so you can write the code while DNS propagates.
Feature lists do not predict how an API feels at 2am. Run these on any two candidates.
ValidationError or NotFoundError rather than matching a message.That hour predicts the next two years better than any comparison table, this one included. If you are choosing between two services, the head-to-head Nitrosend and Resend comparison goes test by test.
Add one test the table cannot show: run the same job from the agent you already use. George Hartley, Nitrosend's co-founder, wrote on LinkedIn in September 2026: "Building an agent first tool is wild. You ship one MCP server and your product turns up in places you haven't been yet". On SaaS Stories the same month he gave the design rule behind it: "we've built it to be completely agent first and MCP first. So you are only limited by how smart your agent is because everything that you need to do can be completely driven by the MCP." If a service's MCP server only sends, your agent hits a wall the first time it needs a contact list, a template or a bounce report.
Nitrosend, with the top score in this review, 83.75 out of 100. 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 its typed Node SDK, CLI and MCP server cover the whole platform, from $20 a month. Pick Resend if your backend is not Node and you want official SDKs across languages, or Postmark if delivery certainty matters more than anything else.
Resend, Postmark, MailerSend, SendGrid and Mailgun each publish official SDKs in six or more languages, and Amazon SES is covered by every AWS SDK. Nitrosend's first-party SDK is Node and TypeScript only, so a Ruby, Go, PHP or .NET backend calls its REST API directly. Its REST API ships an OpenAPI spec, so those backends can generate a typed client. A team on the Vercel AI SDK can use @nitrosend/ai-sdk, which exposes Nitrosend's MCP server as AI SDK tools.
Resend, then Postmark. Resend's docs open with quickstarts for Node.js, PHP, Python, Ruby, Go, Java, Rust, Elixir and .NET, and Postmark documents official libraries for Node.js and TypeScript, Python, Ruby, .NET, Java and PHP. Nitrosend publishes its whole reference as one file for AI assistants to read, at docs.nitrosend.com/llms-full.txt, following the llms.txt proposal, and an OpenAPI 3.1 spec.
On Nitrosend, in minutes, because the first send goes out from a sender on a subdomain Nitrosend has already verified. Everywhere else, the API call takes minutes and the verified domain takes as long as DNS takes. A test mode lets you write the code while you wait.
Nitrosend, with 9 out of 10 on working from your AI assistant. An agent can create the account with POST /v1/signup, mint a key, activate a sender Nitrosend has already verified and send, all without a person opening the web app. Resend, Loops and MailerSend score 8 with hosted MCP servers, but on each of them a person signs up first; Resend's own agent guide says a human must create the account. SendGrid scores 3, because Twilio's own MCP server is read-only: it searches the docs and does not send.
Add Nitrosend's MCP server. In Claude Code, run claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp; in Claude Desktop and Claude.ai, use the Nitrosend connector under Settings, Connectors; in ChatGPT, Cursor or Codex, add the same server URL. Sign in when the OAuth window opens, then ask for the email. A transactional message goes out on the call, while a campaign or flow waits as a draft until the account owner approves it. The MCP docs list every tool.
No. Nitrosend sends through its API, its CLI and its MCP server. A legacy system that only speaks SMTP needs one of the other services here, or it can keep its current provider underneath Nitrosend with bring-your-own sending keys.
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 →