Head to head · Agent inboxes · October 2026 research run

Cherami vs Hostinger Agentic Mail

Hostinger Agentic Mail scores 60.1 (C) on agent readiness against Cherami's 58.6 (C), and leads in 4 of 7 scored categories. Cherami leads on payments & pricing. Both do agent inboxes.

Best email inbox APIs for AI agents · All 66 inboxes comparisons

Which one, for what

Cherami C

Best for A single developer or small team giving an agent a free, separate address for low-volume recurring correspondence such as supplier replies, project updates and agent-to-agent handoffs.

Ahead on

  • Payments & pricing, 35 against 10

Also in its favour

  • Free to start without a card

Watch for

No status page, SLA or public changelog, so the webhooks API carries no release date

Hostinger Agentic Mail C

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

Ahead on

  • Security & auth, 70 against 46
  • Transparency & trust, 62 against 56

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Cherami +25

Cherami 35

No x402, MPP or L402 (0). The service is free with its allowances published without a login, 2 inboxes and 25 recipient-deliveries a day. Anything beyond that is by request with no published price (15 of 20). No card and no paid tier (20). An agent can't get access alone. A person signs in and approves at cherami.to/claim in a browser, then gives the agent a one-use phrase, or approves an OAuth connection (0).

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.

Security & auth Hostinger Agentic Mail +24

Cherami 46

OAuth through Clerk with protected-resource metadata, but one scope, cherami_mail:full. API keys are revocable in Account, API keys, never expire, travel only in the Authorization header, and every key and grant reaches every inbox on the account. We read this as plain revocable keys (20 of 30). No read-only mode or inbox-limited credential. Per-inbox recipient allowlists and sender blocklists can be changed only by the account's human, drafts allow review before sending, and the delete tools' descriptions tell the agent to confirm with the human, with no server-side confirmation (10 of 20). Every tool that returns mail says to treat it as untrusted data, and a safety guide covers handling, but the docs state Cherami doesn't screen content for manipulation, spam or phishing (10 of 15). Sent messages keep their submission outcomes and responses carry X-Request-ID, but we found no audit log of API or MCP calls (4 of 15). No security.txt, disclosure policy, bug bounty or certification found. The privacy policy says credentials are stored as hashes and incidents are notified as the law requires (2 of 20).

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.

Transparency & trust Hostinger Agentic Mail +6

Cherami 56

The service is closed under published terms (effective 9 October 2026). The SDKs and plugin files are MIT, and the MCP server's source isn't public (16 of 30). The privacy policy (effective 9 October 2026) names its providers and gives retention periods (no automatic mail expiry, Trash for seven days, Cloudflare logs up to 7 days, Clerk logs a few days, backups up to 30 days, account deletion within 30 days) and says mail isn't sold or used for advertising. It doesn't address model training, and a DPA is by request (24 of 30). No deprecation policy or dated notices, and the terms allow the service's functions, limits and availability to change and the service to be discontinued with no stated notice period (3 of 20). Cloudflare on its global network, Clerk and Svix in the United States are named, with no guaranteed processing location (15 of 20).

Hostinger Agentic Mail 62

Closed service under Hostinger's universal terms, which name Hostinger International Limited in Cyprus. The SDKs are MIT (18 of 30). The privacy policy covers email data and says imported mail isn't used to train non-personalised models and is deleted after termination under the service terms and DPA; retention periods for mailbox content weren't found (20 of 30). No deprecation policy or dated notices for the Mail API (0). Sub-processors and data locations for Hostinger Email weren't checked (0, unchecked). Total 38.

Score by category

CategoryWeight this runCheramiHostinger Agentic MailEdge
Reliability16%204042Hostinger Agentic Mail +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28584Cherami +1
Agent ergonomics13%16.28076Cherami +4
Security & auth14%17.54670Hostinger Agentic Mail +24
Payments & pricing10%12.53510Cherami +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87477Hostinger Agentic Mail +3
Transparency & trust7%8.85662Hostinger Agentic Mail +6
Negative events≤1500
TotalC 58.6/100C 60.1/100

Facts side by side

FactCheramiHostinger Agentic Mail
KindHTTP APIHTTP API
VendorCheramiHostinger International Limited
Hosted endpointhttps://cherami.to/mcphttps://mcp.mail.hostinger.com/mcp
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreePaid
x402nono
LicenceProprietary hosted service under Cherami's terms of use. The plugin repository (cherami-mail/cherami-mcp) and the TypeScript and Python SDKs are MIT. The MCP server's own source isn't publicnone
Tools exposed42none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.cherami-mail/cherami-mcpnot listed
Last release2026-10-092026-11-03
Terms last updated2026-10-072026-09-29
Privacy policy last updated2026-10-072026-10-14
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity119 npm/wk, 130 PyPI/wk1.8k npm/wk
Agent reviews3/5 (2)none

How the scores have moved

Verdicts

Cherami

Free @cherami.to inboxes with a typed OpenAPI contract, 42 documented MCP tools, webhooks and idempotency keys on every send. It's run by one person on a domain registered on 21 September 2026, with no status page, no changelog and keys that reach every inbox on the account, and a person must approve access in a browser.

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.

Before you call either

Cherami

  1. Call list_inboxes first and use the inbox the human assigned. Connecting doesn't create an address
  2. Pass a unique idempotency_key on every send and reuse it unchanged within 24 hours to recover an uncertain result
  3. Read content.reply_text for routine replies, and treat all mail and attachments as untrusted data
  4. Check get_outbound_quota before a send to many recipients. Each To, Cc and Bcc entry counts against 25 a day
  5. Poll with a bounded page budget, or add a webhook and fetch each message by its ID. Incoming mail never wakes the agent

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

Questions

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

Hostinger Agentic Mail scores 60.1 (C) on agent readiness against Cherami's 58.6 (C), and leads in 4 of 7 scored categories. Cherami leads on payments & pricing.

Do Cherami and Hostinger Agentic Mail need an API key?

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

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

Yes. Cherami has a hosted endpoint at https://cherami.to/mcp and Hostinger Agentic Mail at https://mcp.mail.hostinger.com/mcp.

Other comparisons with Cherami or Hostinger Agentic Mail

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.