# Hostinger Agentic Mail vs MailSlurp

> MailSlurp scores 66.7 (B) to Hostinger Agentic Mail's 60.1 (C) for agent inboxes. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp
- Markdown: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp.md (~4,500 tokens)
- 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-07

MailSlurp scores 66.7 (B) on agent readiness against Hostinger Agentic Mail's 60.1 (C), and leads in 3 of 7 scored categories. Hostinger Agentic Mail leads on schema & documentation and maintenance & community. Both do agent inboxes.

- Hostinger Agentic Mail: grade C, 60.1/100, rank #670 of 1510. Markdown https://www.anchorterminal.com/tools/hostinger-agentic-mail.md · JSON https://www.anchorterminal.com/api/v1/tools/hostinger-agentic-mail.json
- MailSlurp: grade B, 66.7/100, rank #359 of 1510. Markdown https://www.anchorterminal.com/tools/mailslurp.md · JSON https://www.anchorterminal.com/api/v1/tools/mailslurp.json
- Best email inbox APIs for AI agents: https://www.anchorterminal.com/best/agent-inboxes/index.md
- All 66 inboxes comparisons: https://www.anchorterminal.com/compare/agent-inboxes/index.md

## Which one, for what

### Hostinger Agentic Mail (C)

Good for: A low-cost real mailbox on the agent's own domain with IMAP-style operations.

Ahead on:
- Schema & documentation, 84 against 72
- Maintenance & community, 77 against 55

Watch for: No idempotency key on send, and the docs give no retry guidance beyond waiting after 429

### MailSlurp (B)

Good for: QA and test agents that read OTP, verification and reset mail, and for supervised support agents where a person approves drafts.

Ahead on:
- Reliability, 75 against 42
- Agent ergonomics, 84 against 76
- Payments & pricing, 32 against 10

Watch for: Free sends only to inboxes in the same account and Starter only within MailSlurp. External sending and custom domains start on Pro at $49.99 a month


## Why the edge

### Reliability: MailSlurp +33

- Hostinger Agentic Mail (42): Graded with the hosted lines. Hostinger's Statuspage at statuspage.hostinger.com has components for Hostinger Mail SMTP inbound and outbound, IMAP and POP3, webmail and backups, but none for the Mail API or the MCP server (14 of 20). The status host's robots.txt disallows /api/ and the history page loads by script, so only the front page's 15 days (23 October to 6 November) were read, with one Outgoing Emails Service Degraded Performance incident; the longer record wasn't read, a limit of our reading (10 of 30). No request rate numbers; daily sending limits per mailbox are published, 1,000 on Starter and 3,000 on Standard and Premium (5 of 15). The docs say to wait after a 429 and warn that repeated hits can block the IP, with no Retry-After or idempotency on send (3 of 15). No SLA for email found (0). No beta label (10). Total 42.
- MailSlurp (75): Graded as a hosted service, on the REST API. status.mailslurp.com is an updown.io page with eight checks, among them the API, email processes, IMAP and SMTP. It shows one month of uptime per check and has no incident log (14 of 20). All eight checks read 100 per cent for 9 September to 9 October 2026 on the 9 October check and for 1 October to 1 November on 1 November, though the API check's "up since" time of 28 October 06:03 UTC shows a short interruption before it. The page shows nothing older, so 3 August to 9 September couldn't be read and the 90-day record is only partly readable (20 of 30). A guide states a limit of 150 requests a second and the pricing page gives monthly quotas per plan. The errors and limits page in the docs has no numbers (13 of 15). The docs describe `retryable`, `retryAfterSeconds` and `Retry-After` on some 429s, warn that 429 also means a plan or sending restriction, and advise bounded backoff. Agent reply, draft send and SMS send operations take an `Idempotency-Key` header (14 of 15). An Enterprise page says MailSlurp targets 99 per cent uptime for the core API, and section 9.2 of the terms says no SLA applies without a signed amendment (4 of 10). No beta label on the API or the MCP server, which reported version 1.5.0 on 9 October (10). The limits, SLA and MCP pages are per the 9 October check, not re-read on 1 November.

### Payments & pricing: MailSlurp +22

- Hostinger Agentic Mail (10): No x402, MPP or L402 (0). Prices are public per mailbox per month, with the lowest only on 48-month prepaid terms (10 of 20). No free plan; a 30-day money-back guarantee after paying (0). Mailboxes and tokens are bought and created in hPanel by a person (0). Total 10.
- MailSlurp (32): No x402, MPP or L402 found (0 of 40). Four plan prices are public, with unit rates for extra device renders, placement tests and AI extraction. The phone and SMS rate table was empty in the page we read, and usage billing for inbox creations beyond a plan has no stated rate (15 of 20). A Free plan at $0 with 500 emails received a month. The page does not say whether signup asks for a card, and we did not sign up (17 of 20). A person signs up in a browser and creates the first key in the dashboard. Agent keys can then be created by API with an account key (0 of 20).

### Maintenance & community: Hostinger Agentic Mail +22

- Hostinger Agentic Mail (77): hostinger-mail-api-sdk 1.19.8 was published on 3 November 2026 (30). 13 SDK releases in the 90 days from 8 August by npm's records, and docs pages updated on 27 October (20). 24/7 support, a feedback endpoint the API and MCP server expose for agents, but no changelog (10 of 15). The mail MCP server isn't in the official MCP registry (the Hostinger entry there is the hosting connector). The SDKs are current (10 of 15). MIT SDKs generated from the spec, CI not read (7 of 10). Total 77.
- MailSlurp (55): Official SDK releases 17.6.0 for Python, Java, Go and PHP were tagged on 26 October 2026, each regenerated with code changes, and the listed `mailslurp-client` for JavaScript on 24 September (30). Since 3 August those are the only dated releases, five SDK tags that count half each (2.5), and there is no public API changelog, so the line for three in 90 days isn't met. The 9 October check met it with v17.3.0 and v17.4.0 of 14 July, which have left the window (0). Closed service with no public API changelog. A support page and a public board for product requests are linked, and we did not test support (6 of 15). The JavaScript, Python, Java, Go and PHP clients are at 17.6.0, while Ruby and C# stay at 17.5.0 from 31 March (13 of 15). The JavaScript client's tests moved to Vitest on 24 September. Its CI status was not read (6 of 10).

### Schema & documentation: Hostinger Agentic Mail +12

- Hostinger Agentic Mail (84): OpenAPI 3.0 at api.mail.hostinger.com/openapi/openapi.json, version 1.3.0, with 28 operations on 20 paths, none without a description (25). docs.hostinger.com serves llms.txt and a Markdown copy of each page (10). Descriptions say what each call does and side effects, such as text and source reads not changing the seen flag and list pointing to search for filters (16 of 20). Typed parameters and bodies with required fields (12 of 15). Every operation documents 401, 403, 500 and 502, 22 document 422, with a shared error shape and a stable `code` (14 of 15). Version in the path and the spec, but no changelog was found (7 of 15). Total 84.
- MailSlurp (72): OpenAPI 3.0.1 at `api.mailslurp.com/v2/api-docs/`, version 6.5.2, 846 operations on 676 paths on 1 November 2026 (25). `llms.txt` and a Markdown copy linked from each docs page (10). 339 of 846 operations have no description and 93 no summary. The 61 `/agent` operations all have a summary and most name the permission checked. The MCP tool definitions need a credential and were not read (12 of 20). 618 enums, required fields, `uuid` and `date-time` formats and size maxima. Inbox creation takes its options as query parameters and the error `details` field is a free object (12 of 15). Only seven operations document a non-2xx response, four agent work-item calls and three downloads with a `default` response. The docs have a table of status codes and next actions, the file has an `AgentApiErrorDto` schema, and the SDK pages carry examples (8 of 15). The file carries a version number and marks nine operations deprecated. No API changelog was found, and the JavaScript client's CHANGELOG.md has no dates and jumps from 15.12.0 to 17.5.0 (5 of 15). The docs also name `/account/agent-api-keys` paths that are not in the file.

### Agent ergonomics: MailSlurp +8

- Hostinger Agentic Mail (76): 28 REST operations and a remote MCP server whose tool count isn't published. Text-only message reads and page sizes up to 100 keep responses small (18 of 25). page and perPage up to 100 with totals, folder filters and a search endpoint with sort (20). A stable error `code` with a readable message and params, and 207 with per-UID outcomes on bulk flag updates (18 of 20). No idempotency key on send, and MCP annotations couldn't be read (5 of 20). Official SDKs for TypeScript, Python and PHP and a CLI (15). Total 76.
- MailSlurp (84): Graded on the REST API, with the MCP server noted. Agent lists return previews with `size` defaulting to 20 and capped at 100, and `GET /agent/emails/{emailId}/summary` returns a compact message. The MCP docs list 16 tools, whose definitions were not read (20 of 25). `page`, `size`, `sort`, `since` and `before` on lists, a search operation per inbox and wait operations with a deadline (20). Agent errors carry `code`, `message`, `retryable`, `suggestedAction` and `requestId`. The docs say these fields are not on every failure, and the OpenAPI file documents no error response (15 of 20). `Idempotency-Key` on ten operations, among them agent replies, draft sends and SMS sends, plus `expectedConversationVersion` on replies. The standard send operation has none, and MCP annotations were not read (14 of 20). `POST /inboxes` needs no parameter, and the docs list SDKs for ten languages (15).

## Score by category

| Category | Weight | Hostinger Agentic Mail | MailSlurp | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 42 | 75 | MailSlurp +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 72 | Hostinger Agentic Mail +12 |
| Agent ergonomics | 13% (16.2 this run) | 76 | 84 | MailSlurp +8 |
| Security & auth | 14% (17.5 this run) | 70 | 70 | even |
| Payments & pricing | 10% (12.5 this run) | 10 | 32 | MailSlurp +22 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 77 | 55 | Hostinger Agentic Mail +22 |
| Transparency & trust | 7% (8.8 this run) | 62 | 60 | Hostinger Agentic Mail +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **60.1 · C** | **66.7 · B** | |

## Facts side by side

| Fact | Hostinger Agentic Mail | MailSlurp |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Hostinger International Limited | Pettman OÜ |
| Hosted endpoint | `https://mcp.mail.hostinger.com/mcp` | `https://api.mailslurp.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Price for agent inboxes | not published | $1 per transaction |
| x402 | no | no |
| Licence | none | Proprietary service under MailSlurp's terms. The JavaScript client on GitHub is MIT |
| Tools exposed | none | 16 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-26 |
| Terms last updated | 2026-09-29 | 2026-01-16 |
| Privacy policy last updated | 2026-10-14 | 2026-01-16 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1.8k npm/wk | 201k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

## How the scores have moved

### Hostinger Agentic Mail

No score change since it was listed.

### MailSlurp

- -1.7 on 1 November 2026: time
- -0.1 on 28 October 2026: correction
- +0.1 on 27 October 2026: checklist

## Verdicts

**Hostinger Agentic Mail.** A real mailbox behind a typed API, with order- and mailbox-scoped tokens, outgoing allow lists, a remote MCP server and SDKs in three languages. Sends take no idempotency key, request limits have no numbers, and there is no free plan; every mailbox is bought in hPanel on a long prepaid term.

**MailSlurp.** Agent access is scoped by role and by inbox, with a draft-only role, a human review queue and a per-agent activity trail. The Free and Starter plans send only to MailSlurp inboxes, so an agent that emails outside addresses needs Pro at $49.99 a month, and the terms describe every availability figure as a goal.

## Before you call either

### Hostinger Agentic Mail

1. Call `GET /api/v1/me` first to get the mailbox resource IDs the token can reach
2. Ask the owner to set an outgoing allow list before letting an agent send unattended
3. Check the Sent folder before retrying a send, since sends have no idempotency key
4. Read message text with the text-content endpoint, which doesn't mark the message as seen
5. Back off on 429; repeated limit hits can block your IP address for a while

### MailSlurp

1. Create a scoped agent key or connect by MCP OAuth. A normal account key is refused by the MCP agent tools
2. Call `GET /agent/capabilities` or `mailslurp.list_accessible_inboxes` first. Inbox and email IDs outside the granted scope are refused
3. Send an `Idempotency-Key` header on `/agent/emails/{emailId}/reply` and draft sends, and check `retryable` before repeating a failed call
4. Don't sleep and retry on every 429. MailSlurp also uses 429 for plan and sending restrictions
5. Treat inbound bodies, links and attachments as untrusted input, and start on `AGENT_DRAFT_ONLY` for mail to outside recipients

## Questions

### Which is better for AI agents, Hostinger Agentic Mail or MailSlurp?

MailSlurp scores 66.7 (B) on agent readiness against Hostinger Agentic Mail's 60.1 (C), and leads in 3 of 7 scored categories. Hostinger Agentic Mail leads on schema & documentation and maintenance & community.

### Do Hostinger Agentic Mail and MailSlurp need an API key?

Hostinger Agentic Mail needs an API key. MailSlurp takes an API key or an OAuth sign-in.

### Can an agent call Hostinger Agentic Mail and MailSlurp without installing anything?

Yes. Hostinger Agentic Mail has a hosted endpoint at https://mcp.mail.hostinger.com/mcp and MailSlurp at https://api.mailslurp.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "hostinger-agentic-mail", "b": "mailslurp"}`. From a terminal: `anchor compare hostinger-agentic-mail mailslurp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hostinger-agentic-mail.json and https://www.anchorterminal.com/api/v1/tools/mailslurp.json

## Other comparisons with Hostinger Agentic Mail or MailSlurp

- [AgentMail API + MCP vs Hostinger Agentic Mail](https://www.anchorterminal.com/compare/agentmail-vs-hostinger-agentic-mail.md)
- [AgentMail API + MCP vs MailSlurp](https://www.anchorterminal.com/compare/agentmail-vs-mailslurp.md)
- [Cherami vs Hostinger Agentic Mail](https://www.anchorterminal.com/compare/cherami-vs-hostinger-agentic-mail.md)
- [Cherami vs MailSlurp](https://www.anchorterminal.com/compare/cherami-vs-mailslurp.md)
- [Clawpost vs Hostinger Agentic Mail](https://www.anchorterminal.com/compare/clawpost-vs-hostinger-agentic-mail.md)
- [Clawpost vs MailSlurp](https://www.anchorterminal.com/compare/clawpost-vs-mailslurp.md)
- [Hostinger Agentic Mail vs Inbound](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-inbound.md)
- [Hostinger Agentic Mail vs InboxAPI](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-inboxapi.md)
- [Hostinger Agentic Mail vs Lumbox](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-lumbox.md)
- [Hostinger Agentic Mail vs Mailows](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailows.md)
- [Hostinger Agentic Mail vs mails.ai Agent Email](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mails-ai.md)
- [Hostinger Agentic Mail vs Postfleet](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-postfleet.md)
- [Hostinger Agentic Mail vs Robotomail](https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-robotomail.md)
- [Inbound vs MailSlurp](https://www.anchorterminal.com/compare/inbound-vs-mailslurp.md)
- [InboxAPI vs MailSlurp](https://www.anchorterminal.com/compare/inboxapi-vs-mailslurp.md)
- [Lumbox vs MailSlurp](https://www.anchorterminal.com/compare/lumbox-vs-mailslurp.md)
- [Mailows vs MailSlurp](https://www.anchorterminal.com/compare/mailows-vs-mailslurp.md)
- [mails.ai Agent Email vs MailSlurp](https://www.anchorterminal.com/compare/mails-ai-vs-mailslurp.md)
- [MailSlurp vs Postfleet](https://www.anchorterminal.com/compare/mailslurp-vs-postfleet.md)
- [MailSlurp vs Robotomail](https://www.anchorterminal.com/compare/mailslurp-vs-robotomail.md)

---

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