Shipmail vs MailAnvil: Email Hosting With an API vs a Dedicated Transactional Email API
Shipmail (shipmail.to) keeps appearing in "email for AI agents" roundups, and Indonesian developers searching for an email API sometimes land on it. It is not the same category of product as MailAnvil — and that difference decides which one your product needs. Many teams, in fact, need both. This guide draws the line so you don't spend a week integrating the wrong one.
What Shipmail actually is
Shipmail is business email hosting: webmail, shared inboxes, calendars, newsletters, booking pages — all on your own domain, in one subscription. On top of that it offers a REST API, TypeScript and Python SDKs, webhooks, and an official MCP server so Claude or other agents can read and send from your mailboxes.
Pricing (per Shipmail's own API docs, Sep 2026): Solo $4/mo, Pro $9/mo, Team $29/mo — with pooled sending volumes of roughly 20,000 / 40,000 / 120,000 messages per month shared across your whole organization. Note their marketing pages list lower send quotas (1,000 / 10,000 / 100,000); either way, sending is a quota attached to a hosting plan, not the product's center of gravity.
That's the mental model: Shipmail sells mailboxes. The API exists so your agents and scripts can operate those mailboxes.
What MailAnvil actually is
MailAnvil is a transactional email API. Nothing to host, no mailboxes, no webmail. Your backend calls POST /v1/send and MailAnvil queues, signs (SPF/DKIM), delivers via SES, and streams bounce/complaint/delivery events back to you via webhooks and per-recipient status.
This is the pipeline behind the emails your product sends: OTP verification for a Jakarta fintech, booking confirmations for a travel platform, daily sales reports for a F&B chain's outlets, shipping notifications for an e-commerce store during Harbolnas. Volume scales with your user base — thousands per hour on a discount-day spike — and the API contract (idempotency keys, template interpolation, suppression lists, 99.9%-style deliverability discipline) is what matters, not an inbox UI.
Side-by-side
| Shipmail | MailAnvil | |
|---|---|---|
| Category | Email hosting + agent API | Transactional email API |
| Core product | Mailboxes, webmail, calendars | Send pipeline: queue → DKIM → SES → events |
| Sending model | Pooled quota per org | Per-message API with idempotency + retries |
| Bounce/complaint handling | Webhooks available | Suppression lists + automatic pause thresholds + per-recipient status |
| MCP server | Yes (agent drives your inbox) | Yes (agent sends product email) |
| 100k emails/mo cost | Team $29/mo (≈ Rp 464rb, bundled with hosting you may not need) | Max Rp 749rb — with quota enforcement, warmup, kill switch, log retention |
| IDR pricing, QRIS/GoPay | No (USD) | Yes |
| Bahasa docs & support | No | Yes |
The 100k row is the one to read carefully. Shipmail's Team plan looks cheaper per send — but that quota is pooled across all your mailboxes' regular traffic, rides on a hosting product's sending reputation, and their docs describe a gradual daily ramp with reputation controls for exactly this reason. A product firing OTP bursts at 9 PM has very different requirements than a founder reading mail.
When Shipmail wins
- You need inbox hosting for your team or your AI agents anyway — receipts, replies, calendar.
- Your "API" need is agents managing a handful of mailboxes, not an application firing thousands of programmatic sends.
- Solo founders replacing Google Workspace at $4/mo — genuinely good deal for that job.
When MailAnvil wins
- Your backend sends product email: OTP, invoices, booking confirmations, shipping and refund notices.
- You need deliverability discipline: verified-domain-only sending, per-recipient bounce/complaint tracking, automatic suppression, pause thresholds so one bad batch doesn't torch your domain reputation.
- You bill in Rupiah: pay with QRIS or GoPay, read docs in Bahasa Indonesia, get support in your timezone.
- You want agents to send transactional email from your product, not from someone's shared inbox — MailAnvil's MCP server is purpose-built for that.
The Indonesia math
Resend's Pro is $20/mo for 50k emails (≈ Rp 320rb, plus USD payment friction — many Indonesian corporate cards get rejected for foreign SaaS subscriptions). MailAnvil Pro is Rp 249rb for the same 50k, paid via QRIS. At 100k volume, the gaps between "cheap in dollars" and "cheap and actually payable from Jakarta" get bigger, not smaller.
Verdict
Shipmail is a solid pick if the job is hosting email — mailboxes, webmail, an AI assistant for your personal domain. It's the wrong tool for your app's transactional pipeline. And that's fine: run Shipmail for your team's inboxes if you like it, and run MailAnvil for the OTP and receipts your users depend on. Try MailAnvil free at mailanvil.com — 3,000 emails/month, no credit card, verified domain required.