Email infrastructure for AI agents

Let your AI agents
run real email
conversations.

Send transactional email, receive replies, manage threads, run campaigns and automations, through API or MCP, with per-key limits and approvals built in.

Pay for emails sent. Never for contacts stored.

  • 3,000 emails a month free
  • Inbound included
  • No charge without an upgrade you choose

One URL, every MCP client

  • Claude Code
  • Claude
  • ChatGPT
  • Cursor
  • Codex
  • Gemini CLI
  • VS Code
  • Windsurf

Domain to first send

From zero to sent without an email archaeology degree.

Add your domain, publish the records we return, verify it, send. SendRaven keeps transactional and marketing mail on separate identities, so a newsletter cannot trash the reputation of your password resets.

  1. 01

    Add your domain

    POST /v1/domains

    Creates mail.acme.com and news.acme.com and returns the DNS records to publish.

  2. 02

    Verify

    POST /v1/domains/:id/verify

    Answers verified, or names the record that is still missing.

  3. 03

    Send

    POST /v1/emails

    With an idempotency key. Schedule it in plain words: "in 3 days".

Follow the quickstart from domain to first send

Two front doors

REST when you're coding.
MCP when your agent is.

Call the API from your backend, or connect SendRaven to Claude Code, Cursor, Codex, ChatGPT and other MCP clients. Both reach the same account and obey the same permissions and limits. MCP is not the differentiator. What the agent is allowed to do through it is.

One URL, every MCP client

The server runs remotely and signs in with OAuth, so connecting it is pasting a URL. The tools are the same in every client.

  • Remote, over Streamable HTTP
  • OAuth, or an API key as a Bearer header
  • Named for what an agent is trying to do
  • A held send reports awaiting review
Browse the email MCP server's tools

pick your client

terminal
claude mcp add --transport http sendraven https://mcp.sendraven.ai/mcp

The first tool call opens a browser to sign in and pick a workspace. Nothing else to configure.

The key you carrythe same through either door

Same key, same limits, same suppression list on every door.

Guardrails on the key

Whichever door an agent comes through, it holds a key, not a workspace. So the cap, the allowlist and the approval hold live on the key and are checked on every send.

  • Daily cap counts scheduled and held sends
  • Allowlist checked per recipient
  • Approval hold: drafted, then a person releases it
  • A key may not edit its own limits
Every limit a key can carry
POST /v1/api-keys
{
  "name": "support-agent",
  "scopes": ["emails:send", "threads:read"],
  "daily_send_limit": 200,
  "allowed_recipients": ["@acme.com"],
  "requires_approval": true
}

Checked on every send, before anything is persisted. A workspace quota trips after the damage; these trip before.

Readable by agents

An agent can read this site, and the API, before it has a key.

The description documents are unauthenticated, and the errors are written for a model to act on.

  • claude mcp add --transport http sendraven https://mcp.sendraven.ai/mcp

    Remote server over Streamable HTTP. Signs in with OAuth, or takes an API key as a Bearer header.

  • /llms.txt

    What SendRaven is, which call to reach for, which errors are worth retrying, and the calls that cannot be undone.

  • /openapi.json

    Written by hand rather than generated, so the descriptions say what a schema cannot: which mistakes are expensive.

  • 402, not 429

    Out of plan is not too fast. A client that backs off on 429 would retry a 402 forever; GET /v1/usage lets an agent say so before a large batch.

Pricing without the contact tax

We charge for email.
Not for having
an address book.

Store a thousand contacts or a million. Your bill changes when you send email, not when your audience grows. A contact is a row in a database. We don't charge rent for rows.

A million contacts who receive zero emails cost $0, because zero emails were sent.

Your database grew? Congrats. Your email bill didn't.

Compare every plan
  • Free

    3,000

    emails free

    Every month, no expiry. Sending pauses at the limit, so Free never bills you. A payment method activates sending and is never charged on Free.

  • Standard

    One meter

    $19

    a month, from

    50,000 emails to start, then automatic volume pricing: $109 at 250K, $379 at 1M. No tier to pick.

  • Enterprise

    Custom

    above 3 million

    Negotiated volume rates, dedicated sending, an SLA and net terms. Self-service sending never stops at the line.

  • Unlimited contacts. $0 per contact. Always.

  • Inbound included. Replies are never metered.

  • One plan. Transactional and marketing on the same meter.

One meter

What the same month costs.

See every plan and what's included
100,000 emails / month
SendRaven$35.00
Resend$35.00
Postmark$115.00
250,000 emails / month
SendRaven$109.00
Resend$170.00
Postmark$245.00
1,000,000 emails / month
SendRaven$379.00
Resend$650.00
Postmark$775.00
150,000 contacts
SendRaven$0
Resend$650 marketing plan
Postmarkn/a

Competitor figures are the lowest published price for each volume, overage included, checked 16 September 2026. Ours is the Standard plan at that volume. Full pricing, the comparisons with Resend and Postmark, and where the Resend gap comes from.

See the full comparison

FAQ

Questions about SendRaven

Answered in the first sentence. Each one has a longer page behind it.

What is SendRaven?

SendRaven is email infrastructure for AI agents and the applications they run in: an API and MCP server that sends transactional email and campaigns, receives replies as threads, runs automations, and manages contacts, topics and templates, with limits and human approval on the API key an agent holds. A product by the team of Common Ninja.

Can AI agents receive and reply to email with SendRaven?

Yes. Inbound replies are joined to the message they answer on its Message-ID and stored as a thread, with the quoted history stripped. An agent polls GET /v1/threads?awaiting_reply=true for conversations that need an answer, and replies with reply_to_message_id so the threading headers are set for it.

How is SendRaven different from Resend?

SendRaven adds conversation state and credential-level safety to the email API. Resend is excellent developer email and also ships inbound, broadcasts, topics, automations and an MCP server. SendRaven's differences are a thread object with an awaiting-reply query and stripped reply text, a daily cap, recipient allowlist and approval hold on the API key, and one plan for transactional and marketing mail priced per email sent rather than by contacts.

Does SendRaven charge per contact?

No. SendRaven charges for emails sent, and contacts are $0. There is one meter on every plan, so growing an audience does not change the bill until you mail it.

Can SendRaven handle transactional and marketing email?

Yes, on one API and one plan. Adding a domain creates two sending identities, mail. for transactional and news. for marketing, each with its own reputation, so a complaint spike on a newsletter cannot stop a password reset.

Can I require approval before an AI agent sends email?

Yes. Create the agent's API key with requires_approval and every send it makes becomes a draft held for a person. The call returns status pending_approval, which is not an error; a person releases or rejects it from the dashboard or the API, and an undecided draft expires after 72 hours.

Can I limit who an AI agent emails?

Yes. An API key can carry allowed_recipients, a list of full addresses or whole domains, and a daily_send_limit. Both are checked on every send before anything is stored, a send outside the allowlist answers 403 recipient_not_allowed, and a key cannot edit its own limits.

Does SendRaven support MCP?

Yes. SendRaven runs a remote MCP server that signs in with OAuth or takes an API key, and publishes the same server on npm as @sendraven/mcp. It calls the same REST API, so an agent connected over MCP has exactly the permissions and limits of its key.

What happens when someone replies to an automation?

The sequence stops for that person. Automations end an enrolment on a reply by default (exit_on_reply), and also on an unsubscribe, a hard bounce or complaint, a topic opt-out, or a tag rule. Out-of-office and other automatic replies do not count as a reply.

Is inbound email included?

Yes, on every plan, including Free. Received replies are not metered; only emails you send count toward the plan's 3,000 free or included emails.

Still have questions?

Read the docs

You send a raven. It comes back.

Give your agent a return address.

Start with 3,000 emails a month. Inbound included. Unlimited contacts. Human approval when you want it.