For businesses, developers and AI agents

API-first email infrastructure
as the building blocks of email.

We don't ship the finished product. You build it on top of us, with inboxes, sending, receiving, search and webhooks in one infrastructure.

Inbox

Everything addressed to you, minus spam.

Homepage copy, final round

9:41

Sarah Chen

Invoice 2214 for August

9:12

Northwind Cloud

Can we move Thursday?

8:55

Omar Haddad

Signed contract attached

8:30

Mia Chen

Your code is 481 207

8:02

Lumen

Photos from Saturday

Yesterday

Leo Martin

Your flight to Lisbon is confirmed

Yesterday

Skyline Travel

Quarterly numbers are in

Wed

Ken Ito

Coffee next week?

Tue

Priya Raman

What your clicks call

Runs where you deploy, and inside the tools you build with.

  • Node.js
  • Bun
  • Deno
  • Cloudflare Workers
  • TypeScript
  • Python
  • Ruby
  • PHP
  • Go
  • Java
  • C#
  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf
  • Gemini CLI
  • v0
  • Bolt
  • Lovable
  • Base44
  • Modulify
  • Replit
  • MCP

The building blocks

What are the
building blocks?

Domains, inboxes, sending, receiving and more. Use one on its own or put them together. Every block works the same over REST, the SDKs, the CLI and MCP.

01 Domains

Add a domain, publish the records it gives you, and check them with one call.

POST/domains/{id}/verify200

Records to publish

  • MXacme.comfound
  • TXTacme.comfound
  • CNAME4fqd2._domainkey.acme.comfound
  • CNAMEk7wn8._domainkey.acme.comfound
  • CNAMEp2xr5._domainkey.acme.comfound
  • TXT_dmarc.acme.comfound
{ "receiving": { "verified": true }, "sending": { "canSend": true }}
02 Inboxes

Real addresses on your domains, or a catch-all that takes every address at once.

POST/domains/{id}/addresses201
Want a real one? No account, no key.
03 Sending

Send now or later with one call. Every message reports back, and a retry never sends twice.

POST/emails202
queuedsendingsentdelivered

Response

{ "object": "email", "id": "msg_4b7e05d3", "status": "sent"}

email.delivered [email protected]

04 Receiving

Mail to your addresses lands in threads, parsed and checked before your code sees it.

GET/threads/wait200

Raw message

From: Nina Park <[email protected]>To: [email protected]Subject: Can we move Thursday?DKIM-Signature: v=1; a=rsa-sha256; d=northwind.devContent-Type: multipart/alternative

What your code gets

{ "object": "message_arrival", "threadId": "thr_8f2c1a", "address": "[email protected]", "from": { "email": "[email protected]", "name": "Nina Park" }, "subject": "Can we move Thursday?", "receivedAt": "2026-11-03T09:41:00Z"}
07 Calendar

Events, invitations and free time over one API. Invites go out as email that calendar apps understand, and they sync over CalDAV.

POST/calendar/events201
  • 09:30Design reviewaccepted
  • 11:00Supplier callaccepted
  • 14:00Board preptentative
08 Contacts

One address book for the workspace, with groups, birthdays and duplicates you can merge, synced to phones and mail apps over CardDAV.

POST/contacts201

Every surface

One API,
four ways in.

REST, typed SDKs in seven languages, a command line and MCP reach the same operations, with the same scopes and limits.

Your mailbox

msg_4b7e05d3862c1f0a44b19e2csent

Same mailbox, whichever door the message came through.

The API,
a building block for email.

Every operation is a REST call made with a key. The whole contract is one OpenAPI document, readable without a key.

curl -X POST https://api.nextmail.sh/emails \  -H "Authorization: Bearer $NEXTMAIL_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "from": "Acme Billing <[email protected]>",    "to": ["[email protected]"],    "subject": "Your September invoice",    "html": "<p>The invoice is attached.</p>"  }'

Write one call.

Anything that speaks HTTP can send. TypeScript, Python, Ruby, PHP, Go, Java and C# get typed clients, and every message reports back as it is queued, sent and delivered.

Read the docs: Write one call.
POST/emails202
queuedsendingsentdelivered

Response

{ "object": "email", "id": "msg_4b7e05d3", "status": "sent"}

email.delivered [email protected]

Sending

Send now or later with one call. Every message reports back, and a retry never sends twice.

Read the docs: Sending

API keys

Scoped keys with a sending address, an expiry and a log of every request.

Read the docs: API keys
GET/threads/wait200

Raw message

From: Nina Park <[email protected]>To: [email protected]Subject: Can we move Thursday?DKIM-Signature: v=1; a=rsa-sha256; d=northwind.devContent-Type: multipart/alternative

What your code gets

{ "object": "message_arrival", "threadId": "thr_8f2c1a", "address": "[email protected]", "from": { "email": "[email protected]", "name": "Nina Park" }, "subject": "Can we move Thursday?", "receivedAt": "2026-11-03T09:41:00Z"}

Receiving

Mail to your addresses lands in threads, parsed and checked before your code sees it.

Read the docs: Receiving

OpenAPI 3.1

The whole contract is one public document, readable without a key.

Read the docs: OpenAPI 3.1

The SDK,
a building block for email.

Each operation is a method on the client. The API and the SDKs share the same scopes and limits.

npm install @nextmail/sdk
import { init, nextmail } from '@nextmail/sdk' init({ apiKey: process.env.NEXTMAIL_API_KEY }) const email = await nextmail.emails.send({  from: 'Acme Billing <[email protected]>',  to: '[email protected]',  subject: 'Your September invoice',  html: '<p>The invoice is attached.</p>',}) console.log(email.id, email.status)

Install, then make one call

Install the package, then call the client from your code.

Read the docs: Install, then make one call

TypeScript SDK

A client with zero dependencies for Node 20 and up, Bun, Deno and Cloudflare Workers.

Read the docs: TypeScript SDK
POST/emails201
POST/emails201
Idempotency-Key: invoice:inv_2026_09_4192Same message

Safe retries

A retry with the same idempotency key never sends twice.

Read the docs: Safe retries

MCP,
a building block for email.

Point an MCP client at one URL. Each tool is named for what it does, and it follows what you approve.

607 tools

MCP server

Point a client at one URL and sign in. The tools follow what you approve.

Read the docs: MCP server
  • listThreadsApproved
  • sendEmailWaiting for you

Approval

An app sees only the tools its approval covers.

Read the docs: Approval
  • threads:read
  • contacts:read
  • labels:write
  • emails:send

Scopes

Each tool names the scope it needs, such as threads:read or emails:send.

Read the docs: Scopes

The command line,
a building block for email.

Every SDK method is a command. Add --json to read the result and --dry-run to see the request before anything is sent.

Command line

Every SDK method is a command, with --json, --dry-run and exit codes.

Read the docs: Command line
  • 0 ok
  • 3 auth
  • 4 permission
  • 7 validation
  • 8 rate_limited
  • 9 network

Exit codes

Each command ends with a code, so a script can tell an auth problem from a network one.

Read the docs: Exit codes
nextmail
├─ emails
├─ threads
├─ labels
├─ drafts
├─ contacts
├─ templates
├─ webhooks
├─ domains
├─ files
└─ keys

Commands by namespace

The same groups as the SDK, such as emails, threads and domains.

Read the docs: Commands by namespace

Products

What can you build
with it?

Pick a product to see the blocks it is built from.

Also built from the same blocks

  • Tasks by email
  • Notifications
  • Reply by email
  • Email tests
  • Sales outreach
  • Booking pages
  • File sharing
Agent inbox5 of 9 blocks
  1. 01DomainsPOST /domains/{id}/verify
  2. 02InboxesPOST /domains/{id}/addresses
  3. 03SendingPOST /emails
  4. 04ReceivingGET /threads/wait
  5. 06Live eventsGET /live-events

Also offered by

  • open.email
  • AgentMail
  • openemail.sh

Built to be handed over.
Then left alone.

607

MCP tools

Point a client at one URL and sign in. The tools follow what you approve.

No key to paste

Browser sign-in

The client signs in through your browser, and you approve it.

100B

Requests processed

Calls answered for every workspace, from the SDKs, the CLI and MCP.

10K+

Users

People and teams who use the mail app, the API or the phone app.

100K

Visits

Visits to the website, the web app and the documentation pages.

Everything an inbox does.
Through one connection.

Pick a part to watch it work. Each one is a real tool, command or event.

$ nextmail temp new

One platform

Cancel the stack.

A mailbox, a team plan, the fast client, aliases, who opened it and your product's sending API. Six invoices, six logins, one job.

SubscriptionJob
  • Gmail (cancelled)mailbox
  • Google Workspace (cancelled)team plan
  • Superhuman (cancelled)fast client
  • Fastmail (cancelled)aliases
  • Mailchimp (cancelled)open tracking
  • Resend (cancelled)transactional mail

Instead

Nextmail

What you stop paying

Simplified pay as you go pricing

Sending APIs bill by volume, and most inbox APIs bill by inbox. We sell one paid plan, so one bill covers the sending, the inboxes and the mailboxes.

$0No subscription
Free

Send and receive on one domain with the full API, no card required.

  • 1 domain
  • Unlimited addresses
  • 100 emails a day
  • 3,000 emails a month
  • Unlimited receiving
  • 10 mailbox checks a month
  • 10 GB for uploaded files
  • Full API, MCP and SDK access
  • Not included: Priority support
$25a month
Pro

Unlimited domains, addresses and webhooks, with team members. 100,000 sends a month, then pay as you go.

  • Unlimited domains
  • Unlimited addresses
  • 100,000 emails a month
  • Unlimited receiving
  • 100 mailbox checks a month
  • 250 GB for uploaded files
  • Full API, MCP and SDK access
  • Priority support

Plus the rest of the platform, with more room as the plan grows.

Not included in the plan price

Add-on
Extra sends
Price
$0.40 per 1,000 emails
Add-on
Extra mailbox checks
Price
$1.50 per 100 checks
Add-on
Extra storage
Price
$0.10 per GB a month

With pay as you go, these prices apply past your plan.

Talk to us

Not sure it fits?
Ask the people who build it.

Tell us how your team handles mail today. We will tell you honestly whether Nextmail fits, what moving over involves and what it would cost. Fifteen minutes, no slides.

15 minutes with Nextmail

Free

Video call, at a time you choose

What we can cover

  • Does it fit?Tell us how your team works and we will say plainly whether Nextmail suits it.
  • Moving overBringing your domains, addresses and DNS across, and what to switch in which order.
  • Plans and costWhich plan covers you, what it includes and what you would actually pay.
  • Help with setupOnce you decide, we help you get mail flowing on your own domain.