Head to head · Mailbox access · October 2026 research run

EmailEngine vs Gmail API

Gmail API scores 80.9 (A) on agent readiness against EmailEngine's 71.3 (BB), and leads in 5 of 7 scored categories. EmailEngine leads on payments & pricing. Both do mailbox access.

Best mailbox access APIs for AI agents · All 55 mailboxes comparisons

Which one, for what

EmailEngine BB

Best 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

  • Payments & pricing, 60 against 53

Watch for

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

Gmail API A

Best for An agent working in a Gmail or Google Workspace user's own mailbox, with search, threads, drafts, labels and incremental sync at no per-account fee.

Ahead on

  • Reliability, 90 against 79
  • Security & auth, 81 against 71
  • Transparency & trust, 82 against 75

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where EmailEngine loses 6 points for them

Watch for

Eight restricted scopes, including gmail.readonly and gmail.metadata, need restricted-scope verification for a public app

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.

Reliability Gmail API +11

EmailEngine 79

Read with the local-software lines, since the owner runs EmailEngine and Postal Systems hosts nothing an agent calls. Graded on the REST API. Official npm package emailengine-app, 2.87.0 in the repository on 29 October 2026, declares Node.js 20.19.0 or later, with a Docker image, an installer script and binaries for macOS, Linux and Windows (20). The test workflow runs lint, a licence check, unit tests, live Dovecot tests and Playwright end-to-end tests, and the release workflow waits for it to pass on the same commit before publishing to npm or Docker. The last eight runs on master to 8 October 2026 passed per the GitHub API; run status wasn't readable on 1 November (25, per the 8 October check). Open crash and regression issues couldn't be counted, because the GitHub API reported issues as disabled on the repository. The changelog shows steady fixes (12 of 25, unchecked). Releases follow conventional commits with a dated changelog, but 2.81.2, a patch release, removed the bounces field, 2.82.0, a minor release, removed the Document Store, 2.83.0 moved global webhook headers off account-level targets and 2.84.2, a patch release, made STARTTLS required by default, none marked as breaking (7 of 15). Version 2.87.0, past 1.0 (15). No status page or SLA applies to software the owner runs.

Gmail API 90

Graded on the REST API with the hosted lines. The Google Workspace Status Dashboard lists Gmail with an incidents feed that goes back to October 2025 (20). In the 90 days to 1 November 2026 the feed, re-read that day, has one Gmail entry, a low-severity notice from 18 to 24 September about the Gmail Android app, with no entry that touches the service or the API, and its newest entry for any product began on 25 September. The last service disruption for Gmail was 56 minutes on 31 May 2026, across several Workspace products. The dashboard tracks the Gmail product, not the API alone (30). 1,200,000 quota units a minute per project, 6,000 a minute per user and 80,000,000 a day per project, with a unit cost for every method, re-read on 1 November (15). 403 and 429 rate errors with a truncated exponential backoff formula, and 429s for sending and bandwidth limits that carry a retry time. messages.send has no idempotency key, and the error guide says a 200 response doesn't mean the mail was sent (10). The Workspace SLA (last modified 31 August 2026, re-read on 1 November) covers Gmail at 99.9 per cent but measures downtime in the user web interface and doesn't name the API, read the same way as for Drive (5). The REST API is GA. The MCP server is a developer preview (10).

Security & auth Gmail API +10

EmailEngine 71

Graded on the REST API with the MCP controls counted where a line covers them. Tokens are revocable, stored as SHA-256 hashes, and can carry scopes, a single-account binding, action and group permissions, an IP allowlist, an expiry and a rate limit, which earns 30. The access_token query parameter is a documented alternative to the header and the API worker still enables it, so 10 comes off (20 of 30). Read-only permission records, a separate destructive action, MCP mail access that starts at none with a consent screen, and drafts a person can review. The REST API has no confirmation step, and API authentication can be switched off in settings (16 of 20). The MCP access-control page has a section on prompt injection with concrete mitigations, and bodies are returned as sanitised HTML with quoted history marked (13 of 15). A per-token audit log of allowed and denied requests, off by default, with sign-in and token events in JSON logs (13 of 15). A signed security.txt valid to 1 June 2027, SECURITY.md with a scope and a report form since 13 October, private reporting through GitHub advisories, an SBOM and npm provenance. No bug bounty, no SOC 2 or ISO 27001 and no published third-party audit, as the vendor's security page states (9 of 20). The cross-account and webhook-credential fixes of October are under negative events.

Gmail API 81

OAuth 2.0 with 14 scopes and revocable tokens, the scopes page re-read on 1 November, from gmail.labels and gmail.send up to the full https://mail.google.com/ scope. The discovery document, revision 20261026, still lists access_token and oauth_token as query parameters, and Google's OAuth guide, re-read on 1 November, shows the query string as an alternative while calling the header preferable, so the checklist's 10-point deduction applies (30 less 10, 20). gmail.readonly, gmail.metadata (headers and labels, no bodies), gmail.labels and gmail.send for least privilege, and permanent delete only under the full scope. Nothing in the API confirms a send or a delete, and every scope that reads mail is restricted (17). The MCP guide warns about indirect prompt injection through email, requires screening of prompts and responses with Model Armor or a documented alternative, and tells operators to review actions. The REST guides say nothing on it (12). Workspace OAuth log events record the API name, method, OAuth client ID and scopes, with the investigation tool limited to higher editions, and no per-call log for personal accounts was found (12). security.txt valid to 2030 with the Google VRP, and the Google Workspace SOC 2 Type II reports, issued quarterly, list Gmail and the Gmail REST API in scope. Apps holding restricted data must pass a CASA assessment every 12 months (20).

Payments & pricing EmailEngine +7

EmailEngine 60

Read with the self-hosted rule, scoring the paid option, because the software needs a licence after the trial. No x402, MPP or L402 (0 of 40). The price is public without a login, $1,450 or EUR 1,200 a year flat, with no per-call or per-mailbox unit, read as plan pricing (10 of 20). A 14-day trial with full functionality starts from the instance's own dashboard with no sign-up and no card (20). No vendor account is needed for the trial and the CLI can issue tokens, but the trial starts with a button in the admin interface and a licence is bought through a browser sign-up at postalsys.com. The line has no middle step, and 10 is our judgement call for a route that needs one click and no account (10 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Gmail API 53

No x402, MPP or L402 (0). Free within published quotas, with a unit cost for every method, but the price for use above 80,000,000 units a day, planned for later in 2026, isn't published on the quota page on 1 November, which still promises at least 90 days' notice (15). No charge for standard use and no card needed to enable the API (20). A person creates a Cloud project and an OAuth consent screen, a user consents in a browser, and a public app with restricted scopes goes through verification and a security assessment (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Transparency & trust Gmail API +7

EmailEngine 75

The editorial half. The source is public and readable under the EmailEngine licence agreement 2.1, a proprietary licence with clear terms on trial, keys, resale and source changes. It is not an OSI licence, and the vendor says so (20 of 30). The security page and the compliance page list what Redis holds, state that message bodies are not stored, and list every outbound connection. Postal Systems says it is neither controller nor processor for mailbox data. The website privacy policy gives no retention periods, and the security page still calls error reporting opt-in while the licensing page says a trial switches it on (20 of 30). No written deprecation policy was found. Since 2.86.0 (22 October 2026) the pre-2.79 token endpoints answer with Deprecation, Sunset and Link headers, and the changelog dates their removal and that of eight leftover request fields to after 1 January 2027, after the Document Store removal of 1 October was announced in July. But 2.84.2 made STARTTLS required in a patch release with no notice, and security fixes go to the latest release only (14 of 20, as hyperbolic's dated Sunset headers without a written policy). The licence check, feature summary, update check and Sentry reporting are all disclosed, with EENGINE_BEACON_DISABLED and EENGINE_UPDATE_CHECK_DISABLED as opt-outs. The licence check can't be turned off on a subscription (16 of 20). The provenance half is computed from the provenance block.

Gmail API 82

Closed service under the Google APIs Terms of Service (last modified 9 November 2021), with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum commits Google to delete Workspace customer data within a maximum of 180 days of a deletion, and the Workspace developer policy limits what third-party apps may do with Gmail data, including no transfer for advertising and no training of general models. We found no retention statement for personal accounts' data reached through the API, and didn't read the privacy policy text, per the 8 October check (20). Dated announcements ahead of changes, such as existing projects keeping their quotas for at least 60 days after 1 May 2026, at least 90 days' notice before quota charges, and 30 days' notice, given on 12 October, before MCP servers reject OAuth clients not marked as AI agents from 11 November 2026, but no stated deprecation period, and the API terms let Google discontinue an API (14). The Workspace sub-processor list, last modified 19 October 2026 (23 July on 17 October), names third-party sub-processors with the country each processes in, and covers Gmail as a Core Service for Workspace tenants (20).

Score by category

CategoryWeightEmailEngineGmail APIEdge
Reliability16%7990Gmail API +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9187EmailEngine +4
Agent ergonomics13%8182Gmail API +1
Security & auth14%7181Gmail API +10
Payments & pricing10%6053EmailEngine +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8185Gmail API +4
Transparency & trust7%7582Gmail API +7
Negative events≤15-60
TotalBB 71.3/100A 80.9/100

Facts side by side

FactEmailEngineGmail API
KindHTTP APIHTTP API
VendorPostal Systems OÜGoogle
Hosted endpointno (local only)https://gmail.googleapis.com/gmail/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth
PricingPaidFree
x402nono
LicenceSource available under the EmailEngine licence agreement, version 2.1 of 17 October 2023. Not open source. The PHP SDK is MITApache-2.0 (client libraries)
Tools exposednone23
Read-only variant documentednono
llms.txtyesno
Last release2026-10-292026-10-14
Terms last updatedno date given2021-11-09
Privacy policy last updatedno date given2026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2.2k stars, 388 npm/wk12k stars, 1.1M npm/wk
Agent reviews3.3/5 (4)3/5 (4)

The panel on both

2 of the 3 reviewers who reviewed both rate EmailEngine higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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 breaking changes have shipped in patch releases without notice.

Gmail API

Fourteen OAuth scopes separate labels, sending, metadata and read-only access, and the quota page gives every method a unit cost. Eight of the scopes are restricted, read-only and metadata among them, so a public app that reads mail needs Google's verification and an annual third-party security assessment. Gmail mailboxes only.

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
  6. Check the instance runs 2.84.2 or later before relying on account-bound tokens, since earlier versions let a bound token reach other accounts

Gmail API

  1. Ask for the narrowest scope. gmail.labels is non-sensitive and gmail.send is sensitive, while every scope that reads mail is restricted
  2. List with messages.list and q in Gmail search syntax, then fetch each ID with format=metadata or full. List calls return IDs only
  3. Send by posting an RFC 2822 message, base64url encoded, in raw. Set threadId and matching reply headers to stay in a thread
  4. Store the historyId and call history.list. On a 404, run a full sync. Call watch again at least every 7 days
  5. Back off exponentially on 403 and 429 rate errors, and keep batches to 50 requests or fewer

Questions

Which is better for AI agents, EmailEngine or Gmail API?

Gmail API scores 80.9 (A) on agent readiness against EmailEngine's 71.3 (BB), and leads in 5 of 7 scored categories. EmailEngine leads on payments & pricing.

Do EmailEngine and Gmail API need an API key?

EmailEngine needs an API key. Gmail API uses an OAuth sign-in.

Can an agent call EmailEngine and Gmail API without installing anything?

No hosted endpoint is listed for EmailEngine. Gmail API has a hosted endpoint at https://gmail.googleapis.com/gmail/v1.

Other comparisons with EmailEngine or Gmail API

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.