CloudMailin
Long-running inbound email to HTTP service.
CloudMailin has been doing inbound email to HTTP since 2010. Reliable, no-frills, JSON or raw MIME delivery.
An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.
Against inbound parsing into tool calls and model-generated sends that must not duplicate, CloudMailin covers inbound parsing, webhook coverage, event stream, and multi-tenant support, and does not cover idempotency keys, batch sending, and SDK breadth. Whether that gap matters depends on how central those are to the build.
- Inbound parsing: Yes
- Idempotency keys: No
- Webhooks: Yes
- Operating since: Not published
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: No
- SDKs: None
- Multi-tenant: Yes
Not applicable.
Established workloads that depend on a long-running provider.
- › Mature product
- › Multiple payload formats
- › No free tier
- › Older UI
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | None |
| Webhooks | Yes |
| Templates | none |
| React Email | No |
| Batch send | No |
| Scheduled send | No |
| Suppressions | No |
| Multi-tenant | Yes |
| Inbound parsing | Yes |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |