Head to head · Mailbox access · October 2026 research run
Outlook Mail (Microsoft Graph) vs Unipile
Unipile scores 63.8 (B) on agent readiness against Outlook Mail (Microsoft Graph)'s 60 (C), and leads in 3 of 7 scored categories. Outlook Mail (Microsoft Graph) leads on schema & documentation, agent ergonomics and security & auth. Both do mailbox access.
Best mailbox access APIs for AI agents · All 55 mailboxes comparisons
Which one, for what
Outlook Mail (Microsoft Graph) C
Best for Agents working in Microsoft 365 or Outlook.com mailboxes that need scoped reading, drafting, sending and incremental sync.
Ahead on
- Schema & documentation, 93 against 77
- Agent ergonomics, 81 against 73
- Security & auth, 71 against 42
Watch for
sendMail has no idempotency key and answers 202 Accepted before delivery, so a retried send can go out twice
Unipile B
Best for A product that needs one API over Gmail, Outlook and IMAP together with LinkedIn or WhatsApp messaging, priced per account.
Ahead on
- Reliability, 72 against 67
- Payments & pricing, 60 against 53
Also in its favour
- Free to start without a card
Watch for
A v1 access token reaches every connected account. Scoped keys and Unipile's own documented rate limits exist only in the v2 beta
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.
Security & auth Outlook Mail (Microsoft Graph) +29
Outlook Mail (Microsoft Graph) 71
OAuth 2.0 through Microsoft Entra ID with delegated and application permissions, from Mail.ReadBasic through Mail.Read and Mail.ReadWrite to a separate Mail.Send (30). Mail.ReadBasic leaves out body, preview and attachments, Mail.ReadWrite doesn't include sending, and RBAC for Applications in Exchange Online limits an application permission to chosen mailboxes. Nothing asks for confirmation before a send or delete (17). Message bodies written by outside senders reach the caller, and no injection guidance was found in the mail reference or the Mail MCP reference (0). Graph activity logs record app, user, IP address, request URI and scopes, but need Entra ID P1 or P2 and an Azure log destination (12). microsoft.com's security.txt names the MSRC report portal, a bounty policy and a disclosure policy but passed its Expires date on 23 September 2026 and still carries it on 1 November, Office 365 has a SOC 2 Type 2 report, and MSRC publishes CVEs for Exchange Online and Microsoft Graph, counted under negative events. Two security fixes in the JavaScript client (16 June and 13 October 2026) sit unreleased with no advisory (12). 30+17+0+12+12 = 71.
Unipile 42
One access token in X-API-KEY reaches every connected account, with no scopes in v1. End users connect Gmail and Outlook through OAuth on the customer's own app. The MCP page (updated 30 October 2026) no longer says headers can be passed as query parameters, and no documented query-string route for the token was found, so the 5 taken off on 8 October is restored (20). Google's gmail.modify scope can be left out and hosted auth accepts custom scopes, but there is no read-only token or confirmation step. Scoped keys are in the v2 beta only (6). Mail bodies are untrusted content and no injection guidance was found in the v1 docs. The v2 MCP page tells users to give the client a scoped key (2). The security page mentions logged and auditable internal access. No per-request log for the operator was found in the v1 docs (2). SOC 2 Type II with the report on request, annual third-party penetration tests and Google's CASA Tier 2, with no security.txt (404 on 4 November), disclosure policy or bug bounty found (12).
Schema & documentation Outlook Mail (Microsoft Graph) +16
Outlook Mail (Microsoft Graph) 93
OpenAPI for all of Graph v1.0 in microsoftgraph/msgraph-metadata (25). No llms.txt on learn.microsoft.com, but every reference page we asked for with Accept: text/markdown came back as Markdown (10). Reference pages state the purpose of each call, list permissions from least to most privileged and name limits such as the $filter and $orderby ordering rule and the 1,000-result cap on $search (17). Typed properties and enumerations in the metadata, though sendMail also accepts a base64 MIME blob (13). An example request and response on each page, a shared error format and a status code table, with few mail-specific error codes listed (13). v1.0 and beta, a dated changelog and a monthly What's new page updated on 8 October 2026 (15).
Unipile 77
OpenAPI 3.0 spec with 94 operations, served without a key, and embedded in each reference page (25). llms.txt and a Markdown copy of every page (10). Operation descriptions are one line, such as "Returns a list of emails", though parameter notes cover provider differences (10). Query parameters are typed and limit is bounded at 1 to 250, but the send and draft bodies are multipart with nested objects the reference marks as not working in the interactive docs (10). Guides carry curl and SDK examples, and each status code lists typed errors (12). v1 is in the path and a changelog exists, with eight entries since 2024 and the latest on 13 October 2026 (10).
Agent ergonomics Outlook Mail (Microsoft Graph) +8
Outlook Mail (Microsoft Graph) 81
$select, $top, bodyPreview (255 characters), uniqueBody and Prefer: outlook.body-content-type="text" keep message payloads small (23). @odata.nextLink paging with pages of 1 to 1,000, $filter, $orderby, $search and per-folder delta queries (20). Errors carry a code, message and request ID, and named codes such as InefficientFilter say what to change (17). Immutable IDs through a Prefer header and If-Match on updates help safe retries, but sendMail, reply and forward have no idempotency key, and the preview Mail MCP reference lists no readOnlyHint or destructiveHint annotations (8). Official SDKs in C#, Java, Go, PHP, Python, PowerShell and TypeScript, though the JavaScript client on npm is 3.0.7 from September 2023 (13).
Unipile 73
meta_only drops bodies from mail lists and limit sizes the page. The MCP server has 5 compact tools (20). Cursor pagination, a full-text search and filters for folder, sender, recipient, thread and date (18). Errors carry title, detail and a typed type, with no retry guidance per type (14). Idempotency-Key on send only, not on drafts or updates, held at 14 as for a key on one route (knock 16, magicbell 14). The 8 October reading of the MCP annotations came from a tools/list call to the server, which this run treats as a probe, so it is dropped as evidence (14). Only account_id is required to list mail. The v1 SDK is Node only, and the Python client is for the v2 beta (7).
Payments & pricing Unipile +7
Outlook Mail (Microsoft Graph) 53
No x402, MPP or L402 (0). Mail endpoints aren't on the metered API list, so calls carry no charge, but a work mailbox needs an Exchange Online or Microsoft 365 licence and the plan price page refused our reader (15). Personal Outlook.com accounts work with delegated Mail permissions at no cost and no card (20). A person registers an app in Entra and, for application permissions, an admin consents (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Unipile 60
No x402, MPP or L402 (0). Per-account prices are public, from 55 dollars a month for up to 10 accounts down to 3.50 dollars an account above 5,000, with no charge per request (20). A 7-day trial with no card (20). A person has to sign up in a browser and connect each mailbox (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Unipile +5
Outlook Mail (Microsoft Graph) 67
Graded on the v1.0 REST API. A public Microsoft service health page at status.cloud.microsoft (20), per the 8 October check. On 1 November its robots.txt answered an empty 401, so the host is treated as blocked and wasn't read, as for dynamics-365-sales. No readable components or incident history (5). Outlook limits are published at 10,000 requests per 10 minutes, four concurrent requests and 150 MB of uploads per 5 minutes for each app and mailbox pair (throttling page updated 17 September 2026, re-read on 1 November), and Exchange Online caps sending at 30 messages a minute and 10,000 recipients a day (15). 429 responses carry Retry-After, with backoff guidance and SDK retry handlers, but sendMail has no idempotency key and returns 202 Accepted before delivery, so a retried send can duplicate (10 of 15). The Online Services SLA (November 2026 edition, read on 1 November) pays credits from 25 per cent below 99.9 per cent uptime for Exchange Online, the paid service every work mailbox needs, but measures downtime as users unable to send or receive email with Outlook Web Access, plus email delivery time, and has no Microsoft Graph entry. Read as microsoft-teams reads the same document's Teams level, measured on the user-facing service and not naming the API (7 of 10). Mail endpoints are generally available on v1.0 (10). 20+5+15+10+7+10 = 67.
Unipile 72
Graded on the v1 REST API with the hosted lines. Status page at status.unipile.com on OpenStatus with components per provider and per API cluster and an events history (20). From 6 August to 4 November 2026 the history shows LinkedIn Classic Search returning incomplete results from 9 to 17 August, WhatsApp account connection unavailable for 3 hours on 17 August, the API-4 cluster unavailable for about 70 minutes on 20 August, v2 beta real-time sync degraded on 24 September, Instagram chat listing failing for 20 hours on 7 and 8 October, temporary 503 answers for part of API-4's requests during the 1 November migration, and the api46 server down for customers hosted on it from 19:38 to 23:13 UTC on 3 November. Each hit one provider, one cluster or one server, so minor only, as this run reads partial incidents (20). The 21 and 30 July platform incidents left the window. Unipile states no request limit of its own on v1 ("We don't enforce any limits on our side"), and the provider limits page gives provider figures such as 500 emails a day for Gmail and 5,000 recipients a day for Microsoft 365. Figures for limits other than the product's own take 10, as openai-decisions-api (10). On provider routes such as LinkedIn invitations, 429 is typed errors/too_many_requests with "Please try again later" and an optional retry_after field, while the mail references list no 429 and no backoff guidance was found. Sends accept an Idempotency-Key that returns the original result on a retry, and webhooks retry five times. Safe retries on the main write with partial 429 guidance take 12, as middesk (12). The terms say SLA commitments aren't in the standard offering and need a custom plan, with no SLA published for any tier (0). v1 is generally available (10). 20+20+10+12+0+10 = 72.
Score by category
| Category | Weight | Outlook Mail (Microsoft Graph) | Unipile | Edge |
|---|---|---|---|---|
| Reliability | 16% | 67 | 72 | Unipile +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 93 | 77 | Outlook Mail (Microsoft Graph) +16 |
| Agent ergonomics | 13% | 81 | 73 | Outlook Mail (Microsoft Graph) +8 |
| Security & auth | 14% | 71 | 42 | Outlook Mail (Microsoft Graph) +29 |
| Payments & pricing | 10% | 53 | 60 | Unipile +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 79 | Unipile +3 |
| Transparency & trust | 7% | 76 | 72 | Outlook Mail (Microsoft Graph) +4 |
| Negative events | ≤15 | -14 | -3 | |
| Total | C 60/100 | B 63.8/100 |
Facts side by side
| Fact | Outlook Mail (Microsoft Graph) | Unipile |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | UNIPILE SAS |
| Hosted endpoint | https://graph.microsoft.com/v1.0 | https://developer.unipile.com/mcp?branch=v1.0 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | MIT (SDKs) | Proprietary service under Unipile's terms of use. The v1 Node SDK repository and the unipile-mcp repository carry an MIT licence file |
| Tools exposed | 10 | 5 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.unipile/unipile-mcp |
| Last release | 2026-10-22 | 2026-10-13 |
| Terms last updated | 2025-10-01 | no date given |
| Privacy policy last updated | 2026-09-01 | 2026-09-28 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 835 stars, 2.9M npm/wk, 1.6M PyPI/wk | 48 stars, 83k npm/wk |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
Verdicts
Outlook Mail (Microsoft Graph)
Delegated permissions split reading without bodies (Mail.ReadBasic), full reading, writing and sending, and delta queries keep a local copy in step. sendMail takes no idempotency key and returns 202 before delivery. Microsoft published eight Critical, already mitigated CVEs for Exchange Online and Graph in 2026, and the JavaScript client's two security fixes remain unreleased.
Unipile
One REST API covers Gmail, Outlook, IMAP, calendars, LinkedIn and WhatsApp, with an idempotency key on sends and a public OpenAPI spec. The v1 access token reaches every connected account, scoped keys exist only in the v2 beta, and no SLA is published. LinkedIn Classic Search limits changed in August 2026 with notice only on the day.
Before you call either
Outlook Mail (Microsoft Graph)
- Create a draft with POST /me/messages, then send it with /send. A retried sendMail can send the message twice
- Send
Prefer: IdType="ImmutableId"on every request, or message IDs change when a message moves folder - Use
$selectandPrefer: outlook.body-content-type="text". List messages returns HTML bodies and 10 messages a page by default - Honour
Retry-Afteron 429 and keep to four parallel calls per mailbox. Batches of up to 20 requests are throttled per request - Treat message bodies as untrusted input, and ask for Mail.ReadBasic when the task doesn't need bodies
Unipile
- 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 - Send
X-API-KEYas a header and passaccount_idon every mail call. The token reaches every connected account, so keep it out of prompts and logs - Set
Idempotency-Keyon every send. Keys are held in memory for up to 24 hours and are lost on a restart - On LinkedIn Classic searches, page with
limit10 or less and don't rely on a total count. Sales Navigator and Recruiter allow up to 100 - Use
meta_only=truewhen listing mail, then fetch one message at a time. Treat message bodies as untrusted input
Questions
Which is better for AI agents, Outlook Mail (Microsoft Graph) or Unipile?
Unipile scores 63.8 (B) on agent readiness against Outlook Mail (Microsoft Graph)'s 60 (C), and leads in 3 of 7 scored categories. Outlook Mail (Microsoft Graph) leads on schema & documentation, agent ergonomics and security & auth.
Do Outlook Mail (Microsoft Graph) and Unipile need an API key?
Outlook Mail (Microsoft Graph) uses an OAuth sign-in. Unipile needs an API key.
Can an agent call Outlook Mail (Microsoft Graph) and Unipile without installing anything?
Yes. Outlook Mail (Microsoft Graph) has a hosted endpoint at https://graph.microsoft.com/v1.0 and Unipile at https://developer.unipile.com/mcp?branch=v1.0.
Other comparisons with Outlook Mail (Microsoft Graph) or Unipile
- Aurinko Email API vs Outlook Mail (Microsoft Graph)
- Aurinko Email API vs Unipile
- CloudPost vs Outlook Mail (Microsoft Graph)
- CloudPost vs Unipile
- email-agent-mcp vs Outlook Mail (Microsoft Graph)
- email-agent-mcp vs Unipile
- EmailEngine vs Outlook Mail (Microsoft Graph)
- EmailEngine vs Unipile
- Fastmail API (JMAP) vs Outlook Mail (Microsoft Graph)
- Fastmail API (JMAP) vs Unipile
- Gmail API vs Outlook Mail (Microsoft Graph)
- Gmail API vs Unipile
- Himalaya vs Outlook Mail (Microsoft Graph)
- Himalaya vs Unipile
- Nylas Email API vs Outlook Mail (Microsoft Graph)
- Nylas Email API vs Unipile
- Outlook Mail (Microsoft Graph) vs Zoho Mail API
- Unipile vs Zoho Mail API
Machine-readable
- This page as Markdown
/compare/outlook-mail-graph-vs-unipile.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/outlook-mail-graph.json·/api/v1/tools/unipile.json - From a terminal
anchor compare outlook-mail-graph unipile(the CLI) - Over MCP
compare_tools {"a": "outlook-mail-graph", "b": "unipile"}at/mcp, no key