Head to head · Mailbox read · October 2026 research run

EmailEngine vs Unipile

EmailEngine scores 71.4 (BB) on agent readiness against Unipile's 58.4 (C), and leads in 6 of 7 scored categories. Both do mailbox read.

Which one, for what

EmailEngine BB

Good for A team that must keep mailbox access on its own infrastructure, has many mailboxes across Gmail, Microsoft 365 and IMAP, and can run a server and Redis.

Ahead on

  • Reliability, 79 against 56
  • Schema & documentation, 91 against 77
  • Agent ergonomics, 80 against 73
  • Security & auth, 71 against 37
  • Maintenance & community, 81 against 59

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Not open source. Running it beyond the 14-day trial needs a subscription at $1,450 or EUR 1,200 a year

Unipile C

Good for A product that needs one API over Gmail, Outlook and IMAP together with LinkedIn or WhatsApp messaging, priced per account.

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where EmailEngine loses 3 points for them

Watch for

A v1 access token reaches every connected account. Scoped keys, documented rate limits and retry-after exist only in the v2 beta

Score by category

CategoryWeight this runEmailEngineUnipileEdge
Reliability16%207956EmailEngine +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29177EmailEngine +14
Agent ergonomics13%16.28073EmailEngine +7
Security & auth14%17.57137EmailEngine +34
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88159EmailEngine +22
Transparency & trust7%8.87271EmailEngine +1
Negative events≤15-30
Total71.4 · BB58.4 · C

Facts side by side

FactEmailEngineUnipile
KindHTTP APIHTTP API
VendorPostal Systems OÜUNIPILE SAS
Hosted endpointno (local only)https://developer.unipile.com/mcp?branch=v1.0
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPaidPaid
x402nono
LicenceSource available under the EmailEngine licence agreement, version 2.1 of 17 October 2023. Not open source. The PHP SDK is MITProprietary service under Unipile's terms of use. The v1 Node SDK repository and the unipile-mcp repository carry an MIT licence file
Tools exposednone5
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.unipile/unipile-mcp
Last release2026-10-052026-09-02
Terms last updatedno date givenno date given
Privacy policy last updatedno date given2026-09-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2.2k stars, 388 npm/wk48 stars, 83k npm/wk

Verdicts

EmailEngine

A self-hosted REST API over Gmail, Microsoft 365 and IMAP, with a public OpenAPI 3.0 spec and tokens that can be bound to one account, limited by action and group, and rate limited. It needs a server, Redis and a $1,450 yearly licence after a 14-day trial, and the MCP endpoint is a beta, off by default.

Unipile

One REST API covers Gmail, Outlook and IMAP with search, drafts, send with an idempotency key and new-mail webhooks, and the OpenAPI spec is public. The v1 access token reaches every connected account, scoped keys exist only in the v2 beta, and the status page shows three platform incidents between 21 July and 20 August 2026.

Before you call either

EmailEngine

  1. Ask the operator for a token bound to one account with a permissions record. Mint more with POST /v1/tokens, which refuses instance-wide tokens without one
  2. Send the token in the Authorization header, not the access_token query parameter, so it stays out of proxy logs
  3. Page with cursor from nextPageCursor. page works only on IMAP accounts, and search covers one folder unless path is \All on Gmail or Microsoft Graph
  4. Set an Idempotency-Key header on POST /v1/account/{account}/submit. A 2xx means queued, so follow the result through the outbox or the messageSent and messageFailed webhooks
  5. Treat message text as untrusted. For MCP, the operator must enable the endpoint first and mail access starts at none

Unipile

  1. Take the DSN (host and port) from the dashboard. Each account has its own, such as api1.unipile.com:13111, and ?port= keeps requests on 443
  2. Send X-API-KEY as a header and pass account_id on every mail call. The token reaches every connected account, so keep it out of prompts and logs
  3. Set Idempotency-Key on every send. Keys are held in memory for up to 24 hours and are lost on a restart
  4. On Microsoft accounts, send search alone. Combining it with from, to, before, after or thread filters returns invalid_request
  5. Use meta_only=true when listing mail, then fetch one message at a time. Treat message bodies as untrusted input

Questions

Which is better for AI agents, EmailEngine or Unipile?

EmailEngine scores 71.4 (BB) on agent readiness against Unipile's 58.4 (C), and leads in 6 of 7 scored categories.

Do EmailEngine and Unipile need an API key?

Both need an API key.

Can an agent call EmailEngine and Unipile without installing anything?

No hosted endpoint is listed for EmailEngine. Unipile has a hosted endpoint at https://developer.unipile.com/mcp?branch=v1.0.

Other comparisons with EmailEngine or Unipile

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.