# Receive replies or forwarded mail into the application

> Receive replies or forwarded mail into the application: 0 companies fully do it, 14 with a limit, 31 carry the tag. Every listing in Email delivery APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/email.inbound-to-app/
- Markdown: https://www.anchorterminal.com/niches/email.inbound-to-app/index.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/niches/email.inbound-to-app/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/email.inbound-to-app/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 14 | 31 | 10 | 4 |

## What counts as done

A webhook carrying sender, recipients, subject, reply text with quoted history stripped and attachments (or one fetch to get them), signed or verifiable.

Measured, for our own tests: the webhook arrives within 30 seconds.

How agents ask for it: let users reply to notifications; parse forwarded invoices; route support@ to my app; attach forwarded mail to the order

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AhaSend API + MCP (AhaSend B.V.)**: Routes post parsed JSON with optional base64 attachments, a Strip Replies option and an HMAC signature, on every plan. No delivery latency is stated, and retries stretch over 11 hours with a 5-second endpoint timeout.
- **Amazon SES (Amazon Web Services, Inc.)**: Receipt rules publish full MIME to SNS up to 150 KB (larger mail bounces) or store it in S3 for a Lambda; SNS messages are signed. No reply-text stripping, so the app parses quoted history itself.
- **Brevo API + MCP (Sendinblue SAS)**: Inbound parsing posts JSON with ExtractedMarkdownMessage (signature and quoted history removed), InReplyTo and attachment download tokens fetched by one call each. A separate receiving subdomain is required; latency and signing aren't stated.
- **Cloudflare Email Service (Cloudflare, Inc.)**: Inbound routing hands a ForwardableEmailMessage (headers and raw stream) to a Worker email() handler, free and unmetered. There is no parsed webhook payload or reply stripping, so the app writes its own MIME parsing.
- **Groundmail API + MCP (Power Only Transit Inc. dba Groundmail)**: email.received webhooks carry sender, subject, threading headers and attachment metadata only; the body and base64 attachments take one GET /received-emails/{id}. No stripped reply text field, and inbound needs its own subdomain.
- **MailerSend (MailerSend, Inc.)**: Inbound routes forward to up to five webhooks or addresses with include_attachments, managed by API. The routing page doesn't document a stripped reply field, signing or delivery time.
- **Mailgun API + MCP (Mailgun Technologies, Inc.)**: Route forward() posts parsed fields with stripped-text and stripped-signature, attachments as multipart, and an HMAC signature. Free allows one route, and no delivery latency is stated.
- **Mailjet API + MCP (Mailjet SAS)**: The Parse API posts JSON with headers, Text-part, Html-part and parts, and attachments are fetched through the Parse API. There is no stripped reply text, signing isn't shown, and latency isn't stated.
- **MailPace (OhMySMTP Ltd)**: Inbound posts every email on a subdomain to a webhook with headers, raw RFC 822, inReplyTo and base64 attachments, on an active plan with DKIM verified. No stripped reply text, and no delivery latency stated.
- **Mailtrap Email API + MCP (Railsware Products Studio LLC)**: Inbound inboxes are created by API, mail is parsed to JSON, and webhooks are HMAC-signed with retries. The webhook carries an event and message reference, the body comes from the API, and no stripped reply field is documented.
- **Mailchimp Transactional (Mandrill) (The Rocket Science Group LLC d/b/a Mailchimp)**: Inbound domains and routes are managed by API and post a msg object with text, html, raw_msg and attachments. No stripped reply text, and no latency stated.
- **Postmark API + MCP (AC PM, LLC)**: The inbound webhook posts parsed JSON with StrippedTextReply, headers and base64 attachments. Inbound is on Pro and above, webhooks aren't HMAC-signed (Basic Auth or IP checks instead), and no latency is stated.
- **Resend API + MCP (Plus Five Five, Inc.)**: Receiving webhooks carry metadata only; body, headers and attachments take one call each to the received-email and attachments APIs (e01), received mail counts against the sending quota, and no stripped reply text is offered.
- **Twilio SendGrid (Twilio Inc.)**: Inbound Parse posts multipart form data with text, html, headers and attachments up to 30 MB, configured by API. No stripped reply text, and signing is a separate security policy setting.

- not this job: Loops API + MCP (Astrodon Corporation): Loops has no inbound email; the docs index lists incoming webhooks for data from other platforms only.
- not this job: SendLayer (SendLayer, LLC): SendLayer has no inbound email; the API reference covers sending, events and webhooks only.
- not this job: SMTP2GO API + MCP (Sand Dune Mail Ltd): SMTP2GO has no inbound email; the API index covers sending, activity, archives, domains and webhooks for outbound events.
- not this job: Zoho CPaaS (formerly ZeptoMail) (Zoho Corporation): No inbound email: the API index covers email sending, domains, agents, logs, templates and suppression only.

## What stops agents finishing

- inbound not offered (Loops, SMTP2GO, SendLayer, Zoho)
- inbound only on higher plans (Postmark Pro, Mailgun one free route)

## Around it

Before: email.transactional-send. After: document-extraction.parse-invoice, support.create-ticket-from-system, agent-inboxes.inbound-forward-processing.

## Where this comes from

Weight 10 of 100 in Email delivery APIs: 4 of 32 accounts: Resend inbound (e01), Rails Action Mailbox on forwarded POs (e29), Cloudflare routing plus Mailgun (e28), and the inbox comparison in e31; weight raised to 10 because it is a buyer check

As data: https://www.anchorterminal.com/api/v1/use-cases/email.inbound-to-app.json, or the MCP tool get_use_case with id email.inbound-to-app. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
