# Hostinger Agentic Mail vs mails.ai Agent Email

> mails.ai Agent Email scores 65.2 (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-mails-ai
- Markdown: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mails-ai.md (~4,300 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

mails.ai Agent Email scores 65.2 (B) on agent readiness against Hostinger Agentic Mail's 60.1 (C), and leads in 6 of 7 scored categories. 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
- mails.ai Agent Email: grade B, 65.2/100, rank #434 of 1510. Markdown https://www.anchorterminal.com/tools/mails-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/mails-ai.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.

Also in its favour:
- No incidents deducted, where mails.ai Agent Email loses 8 points for them

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

### mails.ai Agent Email (B)

Good for: Agents that send transactional mail and read replies, such as support, notification and verification agents, where an injection score on inbound mail is wanted out of the box.

Ahead on:
- Reliability, 80 against 42
- Agent ergonomics, 83 against 76
- Security & auth, 78 against 70
- Payments & pricing, 30 against 10

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: No company or person named; legal entity details only on request


## Why the edge

### Reliability: mails.ai Agent Email +38

- 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.
- mails.ai Agent Email (80): Graded as a hosted service. Better Stack status page at status.mails.ai with API, dashboard and website components and 90-day bars (20). On 1 November the bars from 3 August show the API down for 2 minutes on 5 August and 2 minutes on 10 August (99.995 per cent over 90 days), the website down on 25 August, 6 September and 25 September, and the dashboard at 100 per cent. The July downtime read on 5 October has left the window. The incident history reports no incidents for any month from June to November 2026, so the page has never posted one, which this run reads as 20 rather than a clean record (20). Send caps published per plan by hour, day and month (15). 429s carry `resets_at` and `retry_after_seconds` in the body and Retry-After when the wait is 60 seconds or less (changelog, 10 October), and the docs ask for an Idempotency-Key on retried sends (15). A 99.9 per cent uptime target with pro-rated credit is on mails.ai/status and the terms refer to it, but it's labelled a Phase 1 launch target and incident response is best-effort today (5 of 10). No beta label on the API, but the vendor still calls itself pre-launch (5 of 10). 20 + 20 + 15 + 15 + 5 + 5 = 80.

### Payments & pricing: mails.ai Agent Email +20

- 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.
- mails.ai Agent Email (30): No x402, MPP or L402 (0). Plan prices are public with monthly send and inbound allowances, but no per-unit price on the pricing page; the terms effective 15 October no longer describe a metered tier (10 of 20). Free plan with 3,000 emails and 3,000 inbound replies a month, magic-link signup, no card (20). Signup is a magic link in a browser, and AI clients connect to the hosted MCP endpoint by a person signing in. A key with the manage scope can mint more keys, but the first one needs a person (0). 0 + 10 + 20 + 0 = 30.

### Security & auth: mails.ai Agent Email +8

- Hostinger Agentic Mail (70): Named tokens scoped to one order and to all or selected mailboxes, with separate SMTP/IMAP and webhook-management permissions, shown once and revocable one by one. The MCP server advertises protected-resource metadata on its 401 but documents bearer tokens only (25 of 30). Outgoing allow and block lists, with the block list winning, and mailbox-level scoping. Deletes are permanent and no read-only permission was named (14 of 20). Inbound mail is untrusted content; the docs advise the allow list for autonomous agents but give no prompt-injection guidance for message content (6 of 15). Email Logs record delivery statuses, sign-in attempts per protocol and an audit trail of mailbox setting changes, and webhooks show the last 20 deliveries (10 of 15). A valid security.txt, a HackerOne bug bounty and a responsible disclosure policy; no certification was checked (15 of 20). Total 70.
- mails.ai Agent Email (78): Bearer keys, scoped to send, read, manage or (since 10 October) draft, bindable to one agent, with optional expiry, stored hashed and revocable at once by API; AI clients connecting to the hosted MCP endpoint sign in by OAuth, and connected apps can be listed and revoked (30). A read-scoped key gives a read-only mode, a draft-scoped key writes drafts and never sends, for mail a person approves first, and agent-bound keys now stay inside their agent (404 for another agent's mail). Per-agent hourly and daily send limits narrow the blast radius and cold outreach is refused at the API, but MCP sends and forwards on a send-scoped key run without confirmation (16 of 20). Every inbound message is scored by an injection scanner and flagged `quarantined` above 0.95, which the docs tell the agent to branch on. The scanner's accuracy is a vendor claim we didn't test (13 of 15). Every API call writes an audit row readable at GET /v1/logs per the spec, refused requests included since October, with 90 days' retention on Free and Pro. We didn't call it (12 of 15). security.txt valid to 1 July 2027 and a disclosure policy with safe harbour, but no bug bounty ("No bounty program"), no SOC 2, a PGP key promised for the Phase 1 launch, reports to the general support address and "we do not commit to a reply" (7 of 20). 30 + 16 + 13 + 12 + 7 = 78.

### Agent ergonomics: mails.ai Agent Email +7

- 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.
- mails.ai Agent Email (83): Since @mailsai/mcp-server 0.3.0 (10 October) every API operation but four is a tool, 73 in 0.5.0 (20 written by hand, 53 generated), which is the over-30 band (5). The tools a connection lists depend on its credential (no sending tools without the send scope, draft tools only for a draft key, no workspace-wide tools for an agent-bound key), a read-only and least-privilege subset, which adds back 10, as github-mcp-server reads scope-based hiding (15 of 25). Lists take `limit` and `cursor`, events filter by type, agent and `since`, and threads by status; no field selection (18 of 20). REST errors carry stable codes, `param` and Retry-After. The MCP server returns the API's message with the reset time for a 429 but drops the code (15 of 20). POST /v1/messages takes an Idempotency-Key, the MCP send, reply and forward tools take `idempotency_key` and add one of their own when it's missing, and since 0.4.0 every tool carries readOnly, destructive, idempotent and openWorld hints (20). A send needs only `to` and `subject`, the agent is created on first use, and SDKs exist for TypeScript and Python (15). 15 + 18 + 15 + 20 + 15 = 83.

## Score by category

| Category | Weight | Hostinger Agentic Mail | mails.ai Agent Email | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 42 | 80 | mails.ai Agent Email +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 84 | even |
| Agent ergonomics | 13% (16.2 this run) | 76 | 83 | mails.ai Agent Email +7 |
| Security & auth | 14% (17.5 this run) | 70 | 78 | mails.ai Agent Email +8 |
| Payments & pricing | 10% (12.5 this run) | 10 | 30 | mails.ai Agent Email +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 77 | 80 | mails.ai Agent Email +3 |
| Transparency & trust | 7% (8.8 this run) | 62 | 65 | mails.ai Agent Email +3 |
| Negative events | ≤15 | 0 | -8 | |
| **Total** | | **60.1 · C** | **65.2 · B** | |

## Facts side by side

| Fact | Hostinger Agentic Mail | mails.ai Agent Email |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Hostinger International Limited | Mails.ai |
| Hosted endpoint | `https://mcp.mail.hostinger.com/mcp` | `https://api.mails.ai/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | Proprietary hosted API under the mails.ai terms of service. The MCP server, the TypeScript SDK and the Python SDK in mailsai/mailsai are MIT |
| Tools exposed | none | 73 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `ai.mails/agent-email` |
| Last release | 2026-11-03 | 2026-10-16 |
| Terms last updated | 2026-09-29 | 2026-05-14 |
| Privacy policy last updated | 2026-10-14 | 2026-05-14 |
| 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 | not found in the text |
| Popularity | 1.8k npm/wk | 650 npm/wk, 116 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Hostinger Agentic Mail

No score change since it was listed.

### mails.ai Agent Email

- -1.6 on 1 November 2026: product, negative event, time
- -0.1 on 28 October 2026: correction
- +0.2 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.

**mails.ai Agent Email.** Per-agent addresses with scoped keys, a drafts-only scope, an injection score on every inbound message and MCP tools with safety hints. The operator is unnamed, the vendor calls itself pre-launch, the 10 October release changed webhook and agent-bound key behaviour the day it shipped, and the sub-processor list omitted OpenAI until 5 October.

## 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

### mails.ai Agent Email

1. Use an `mk_test_` key until the flow works. Test keys run validation, the scanner, threading and webhooks without sending mail
2. Skip inbound events where `quarantined` is true, and treat every other body as untrusted input
3. Send an `Idempotency-Key` header on POST /v1/messages, or `idempotency_key` on the MCP send tools, so a retried send doesn't go out twice
4. Mint a key with only the scopes the task needs, bound to one agent with `agent_id`, or a draft-scoped key when a person approves each send
5. Name thread events explicitly on a webhook endpoint. Since 10 October a `*` subscription no longer receives them

## Questions

### Which is better for AI agents, Hostinger Agentic Mail or mails.ai Agent Email?

mails.ai Agent Email scores 65.2 (B) on agent readiness against Hostinger Agentic Mail's 60.1 (C), and leads in 6 of 7 scored categories.

### Do Hostinger Agentic Mail and mails.ai Agent Email need an API key?

Both need an API key.

### Can an agent call Hostinger Agentic Mail and mails.ai Agent Email without installing anything?

Yes. Hostinger Agentic Mail has a hosted endpoint at https://mcp.mail.hostinger.com/mcp and mails.ai Agent Email at https://api.mails.ai/v1.


## For agents

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

## Other comparisons with Hostinger Agentic Mail or mails.ai Agent Email

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