Compare
Every edge we hold, against the whole field.
A dash means not offered or not documented on the day we looked.
It is not a claim that it cannot be done. Where a competitor is the better choice, its page says so.
Last checked 16 September 2026.
- SendRaven vs ResendThe developer-favourite email API, with inbound, broadcasts and automations, and marketing plans priced by contacts.
- SendRaven vs PostmarkTransactional email with a long deliverability record and mature inbound parsing.
- SendRaven vs MailgunA long-running email API with inbound routes and dedicated IPs; marketing is a separate product.
- SendRaven vs SendGridTwilio's email platform: an Email API sold by volume and Marketing Campaigns sold by contacts.
- SendRaven vs AgentMailInboxes for AI agents: each agent gets its own address, threads and webhooks.
- SendRaven vs LoopsMarketing email for SaaS, priced by subscribed contacts, with transactional included.
- SendRaven vs MailchimpThe marketing email suite, priced by contacts, with transactional as a paid add-on.
| Edge | Resend | Postmark | Mailgun | SendGrid | AgentMail | Loops | Mailchimp | |
|---|---|---|---|---|---|---|---|---|
| Priced per email sent, never per contactPricing by list size charges most to the customer whose list is growing, which is the point of the product. | transactional by volume; marketing $40–$650/mo by contacts | Email API by volume; Marketing Campaigns by contacts | per inbox and per plan: $20/mo for 10 inboxes and 10,000 emails | by subscribed contacts; sends unlimited | by contacts | |||
| Transactional, campaigns and automations on one planTwo products means two suppression lists that disagree and a price gap that rewards mislabelling campaigns as transactional. | two plans, one dashboard | broadcast stream; no audiences or automations | marketing is Mailjet, a separate product | two products | no campaigns or automations | marketing and transactional together; no inbound | transactional is Mandrill, a paid add-on | |
| The reply is a thread, not a webhookA webhook hands you a raw message and leaves you to work out which conversation it belongs to. | a received-email event; you fetch the message and set reply headers yourself | inbound JSON to a webhook | routes post to a webhook | Inbound Parse posts to a webhook | ||||
| Quoted history stripped from repliesThe third reply in a thread is mostly the first two quoted back. A model reading it pays for that and gets confused by it. | text and html, no stripped field | StrippedTextReply | stripped-text on inbound | extracted_text | ||||
| One query for what is awaiting a replyThis is the poll an agent actually runs. Without it you build a state machine over inbound events. | labels and drafts; no awaiting-reply query documented | |||||||
| Per-key daily cap and recipient allowlistA workspace quota trips after an agent has mailed thousands of people. A key limit trips before. | keys scope to a domain and to send-only; no cap or allowlist | domain sending keys; no cap or allowlist | key permissions; no cap or allowlist | per-key permissions and inbox scope; allow and block lists sit on inboxes, not keys | ||||
| Human approval hold on a keyThe only way to let an agent write mail without letting it send mail. | a key can write drafts it cannot send; a person sends them | |||||||
| Campaign refused before it starts on bounce or complaint rateReputation dashboards report the damage. A gate prevents it. | ||||||||
| Unsubscribe cancels queued sends and ends the sequenceDoing only the first is how a working unsubscribe still delivers day three of a welcome series. | an automation skips its remaining send steps for an unsubscribed contact | not documented | not documented | not documented | no sequences | an unsubscribed contact gets no further campaign or workflow email | not documented | |
| Opt down by topic, per personGiven only all-or-nothing, people press spam instead, and a complaint costs the domain far more than an opt-out. | topics on broadcasts | list-level unsubscribes | unsubscribe groups | mailing lists | groups and preferences | |||
| Remote MCP server with no stored credentialsA server that holds its own database credentials is a shared identity for every caller. | official, local or hosted, covering the whole API | official local server, 24 tools; none reads inbound | official local server | Twilio's official server reads the docs; it does not call the API | official remote server | official remote server | Mandrill only, an official remote server; none for marketing | |
| llms.txt and an unauthenticated OpenAPI documentA model decides what it is holding from the description document. Generated ones say what, not which. | llms.txt; OpenAPI on GitHub | llms.txt; Swagger 2.0 at /swagger/server.yml | llms.txt and OpenAPI 3.1 | a section in Twilio's llms.txt; OpenAPI on GitHub | llms.txt and OpenAPI | llms.txt and OpenAPI | llms.txt | |
| Errors written for an agentA client that backs off on 429 retries a payment problem forever. A model that sees an error retries a held draft. | ||||||||
| Inbound included and freeCharging for the reply discourages the half of email that makes it a conversation. | on all plans; each received email counts against the sending quota | Pro and Platform plans | 1 route free, 5 on Basic, full from Foundation | Inbound Parse on every plan | the core product | Mandrill only, parsed JSON to a webhook | ||
| Free tier that does not expire or throttle by the dayA trial that expires is a deadline, not a tier, and a 100-a-day cap is a tier you cannot test a campaign on. | 3,000/mo, capped at 100 a day | 100 emails a month | 100 a day | 60-day trial, 100 a day | 3 inboxes, 3,000 a month, 100 a day | 1,000 contacts, 4,000 sends, branded footer | 250 contacts, 500 sends a month | |
| Rate per 1,000 past the entry paid tierThe rate past the allowance is the real price for anyone who grows. | $0.90 per 1,000 on Pro | $1.80 per 1,000 on Basic | $1.80 per 1,000 on Basic | tiered, $0.0013 to $0.0005 per email by plan | plan-capped | |||
| Usage pricing without tier cliffsTiers do not hurt at the boundaries. They hurt in the middle, which is where most senders live. | tiers, with pay-as-you-go overage between them | steps by contact count | steps by contact count |
- Offered
- Partly, or with a condition
- Not offered, or not documented
Competitor figures are published list prices and public documentation on the date shown.

Pick the page for the tool you are on.
Already decided? The migration guides cover the export, the column mapping and the opt-outs for each tool.

