---
title: "Email APIs for AI agents compared · Workwae"
description: "Workwae, Nylas, Unipile, Aurinko, EmailEngine and the Gmail and Graph APIs compared for agents: scoped keys, draft versus send, MCP servers, webhooks and pricing."
url: https://workwae.com/blog/email-apis-for-ai-agents
---

Blog

# Email APIs for AI agents: how the options compare.

An agent reads text written by strangers and can be talked into things, so what matters is how narrow its key is, whether it can draft without sending, and what each vendor charges per account.

November 11, 2026 · 9 min read

- [Sending](https://workwae.com/blog/tag/sending)
- [Webhooks](https://workwae.com/blog/tag/webhooks)

An email API built for apps assumes the caller is code you wrote. An agent is a model that decides what to call, reads text written by strangers, and can be talked into things. That changes what you need from the API: a credential narrower than “the mailbox”, a way to separate drafting from sending, and tools a model can use without a wrapper you maintain.

This post compares Workwae, Nylas, Unipile, Aurinko, EmailEngine and the native Gmail and Microsoft Graph APIs on those points. Competitor facts come from each vendor’s own documentation, read on October 30, 2026, and link to it. Workwae is our product, so its weaknesses are in the last section. “Not documented” means we found nothing on the pages we read, not that the vendor lacks it.

## What changes when the caller is a model.

- **Credential scope.** What can a leaked or hijacked agent key reach: one mailbox or every one, read or write, send or not?
- **Draft versus send.** Can the agent save a reply for a person without being able to send it?
- **[MCP](https://workwae.com/glossary#mcp).** Is there a server that exposes mail, calendar and contacts as tools, and does the tool list follow the credential?
- **Change delivery.** How does the agent learn that mail arrived: signed webhooks, a feed, or polling?
- **Pricing unit.** An agent can call an API far more than a person does, so a per-call price behaves differently from a per-account one.

Every vendor that documents an MCP server says the same about the risk: instructions inside an email can steer the agent. Nylas calls prompt injection “a real risk” and tells you to require confirmation before sending ([Nylas MCP server](https://developer.nylas.com/docs/dev-guide/mcp/)). EmailEngine says the same and recommends granting no mail access, or read-only access, by default ([MCP access control](https://learn.emailengine.app/docs/mcp/access-control)). The rest of this post is about which controls each product gives you.

## Credentials: who holds the key.

- **Workwae.** API keys carry `read`, `write`, `send` and `admin` scopes that owners and admins set, can be limited to specific accounts, and fail with `missing_scope` outside them. An MCP key is bound to one account. An account token carries every scope on its account, so agents get keys instead ([AI email agents](https://workwae.com/use-cases/ai-agents)).
- **Nylas.** IAM principals bind to one grant, workspace, application or organization and carry roles and permissions. Keys expire (up to ten years), and Nylas keeps config and access audit views for 400 days. A plain application API key reaches every connected account in the application ([Nylas IAM](https://developer.nylas.com/docs/v3/auth/nylas-iam/)).
- **EmailEngine.** Tokens combine MCP scopes, a permissions record of (`read`, `write`, `send`, `destructive`) by section, a binding to one account, IP allowlists, rate limits and expiry. You run it, so you operate the key store too ([access control](https://learn.emailengine.app/docs/mcp/access-control)).
- **Aurinko.** A `scopes` parameter limits what each user’s token can do: `Mail.Read`, `Mail.ReadWrite`, `Mail.Send`, `Mail.Drafts` and calendar and contacts equivalents ([Authentication scopes](https://docs.aurinko.io/authentication/authentication-scopes.md)).
- **Unipile.** Its MCP guide says an access token “gives access to the accounts of your Unipile application”. We found no per-key scopes ([Unipile MCP](https://developer.unipile.com/docs/mcp.md)).
- **Gmail API.** There is no separate agent credential: the agent holds the user’s OAuth grant. Reading mail needs a [restricted scope](https://workwae.com/glossary#restricted-scope), which means Google verification and an annual security assessment if you store the data ([Gmail API scopes](https://developers.google.com/workspace/gmail/api/auth/scopes), [Security assessment](https://support.google.com/cloud/answer/13465431)).
- **Microsoft Graph.** Delegated permissions follow the signed-in user. The app-only `Mail.ReadWrite` permission covers “all mailboxes without a signed-in user”, so an app-only agent needs Exchange’s RBAC for Applications to shrink that ([Graph permissions](https://learn.microsoft.com/en-us/graph/permissions-reference), [RBAC for Applications](https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac)).

## Draft versus send.

The cleanest guarantee is a credential that cannot send at all. How easy that is depends on how the vendor draws the scope lines:

- **Gmail** bundles them. `gmail.compose` is “Manage drafts and send emails”. A grant that can create a draft can send one. `gmail.send` sends without reading, which is the opposite of what a review workflow needs ([scopes](https://developers.google.com/workspace/gmail/api/auth/scopes)).
- **Graph** separates them. `Mail.ReadWrite` creates, reads, updates and deletes mail and “does not include permission to send mail”; `Mail.Send` is its own permission ([permissions](https://learn.microsoft.com/en-us/graph/permissions-reference)).
- **Aurinko** has `Mail.ReadWrite`, which excludes send, but its docs do not say it can save drafts. `Mail.Drafts`, the draft scope, includes sending messages and drafts.
- **EmailEngine** grants `send` separately, and its read-only level cannot send. Its “mail agent” level reads, organizes, drafts and sends.
- **Nylas** adds a handshake on top of IAM: `send_message` and `send_draft` must follow `confirm_send_message` or `confirm_send_draft`, which returns a confirmation hash.
- **Workwae** keeps `send` apart from `write`, which covers drafts. Without `send` the MCP server has no send tool. On top of that sits a send policy for agent sends: `confirm` by default (the user confirms subject, recipients and account), `allow`, or `drafts_only`, plus a daily limit, recipient-domain rules, an undo window and a duplicate guard ([MCP server](https://workwae.com/mcp)).
- **Unipile**: not documented on the pages we read.

One trap applies to all of them: calendar events with attendees make the provider send invitations. Workwae’s MCP tools need `send` as well for those writes. If you want an agent that reaches no one, give it read-only.

send policy

```bash
curl -X PATCH "https://api.workwae.com/v1/settings" \
  -H "Authorization: Bearer $WORKWAE_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "mcpSendPolicy": { "mode": "drafts_only", "dailySendLimit": 50 } }'
```

## MCP servers.

- **Workwae** hosts one at `api.workwae.com/mcp` for mail, calendars and contacts. A client sees only the tools its scopes allow. People sign in with OAuth; backends use an API key.
- **Nylas** hosts `mcp.us.nylas.com` (and an EU host) with 38 tools covering mail, calendar, contacts and its Notetaker, authenticated with an API key or an IAM key. Requests time out after 90 seconds ([docs](https://developer.nylas.com/docs/dev-guide/mcp/)).
- **EmailEngine** ships `/mcp` in the self-hosted server. It is a beta since v2.79.2, off by default, and its tool list is filtered per credential ([docs](https://learn.emailengine.app/docs/mcp)).
- **Gmail** has a remote server at `gmailmcp.googleapis.com`. It needs membership in the Workspace Developer Preview Program and the `gmail.readonly` and `gmail.compose` scopes. Its tools search, read, label and draft; none sends ([reference](https://developers.google.com/workspace/gmail/api/reference/mcp), [setup](https://developers.google.com/workspace/gmail/api/guides/configure-mcp-server)).
- **Microsoft** documents a preview Mail server in Agent 365 with draft, send, reply and search tools, and says to use Work IQ MCP for new projects ([Mail reference](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-mail-tools)).
- **Unipile** serves its API reference to coding agents, with tools such as `search-endpoints` and `execute-request`. It helps an agent write the integration more than it gives an assistant a mailbox ([docs](https://developer.unipile.com/docs/mcp.md)).
- **Aurinko**: no MCP server in its documentation index.

## Change delivery.

An agent that reacts to new mail needs a trigger. Gmail’s native trigger is a Pub/Sub message that holds only a mailbox cursor, and Graph’s is a [change notification](https://workwae.com/glossary#change-notification) that needs delta queries behind it; both expire and need renewal ([Gmail push](https://workwae.com/blog/gmail-push-notifications), [Graph notifications](https://workwae.com/blog/microsoft-graph-change-notifications)). The wrappers hide that to different degrees:

- **Workwae** sends Standard Webhooks signatures, keeps a delivery log with replay, and exposes the same events as an ordered [change feed](https://workwae.com/glossary#change-feed) an agent can poll without a public endpoint ([Webhooks](https://workwae.com/features/webhooks)).
- **Nylas** sends signed webhooks, and can deliver to Google Pub/Sub or Amazon SNS ([notifications](https://developer.nylas.com/docs/v3/notifications/)).
- **EmailEngine** has webhooks and routes, and its management tools list, retry and remove failed deliveries.
- **Aurinko** has a Webhooks API for email, calendar, contacts and tasks, and a guide to configure Pub/Sub for Gmail ([Webhooks API](https://docs.aurinko.io/unified-apis/webhooks-api.md)).
- **Unipile** documents new-email and calendar webhooks ([new email webhook](https://developer.unipile.com/docs/new-emails-webhook)).

## Pricing models.

Most vendors bill by connected account, which suits agents: ten thousand tool calls cost the same as ten. Prices below are as of October 30, 2026.

- **Nylas**: free with 5 accounts; Essentials is $15 a month with 10 accounts and $2.25 for each extra; Pro starts at $49 a month ($43 annual) with 25 accounts. It also sells Agent Accounts, real mailboxes at your own domain for the agent itself ([pricing](https://www.nylas.com/pricing/)).
- **Unipile**: &euro;5 per account a month, at least &euro;49 a month for up to 10 accounts, with no per-request fees ([pricing](https://www.unipile.com/pricing-api/)).
- **Aurinko**: $1 to $2 per active account a month, by APIs and traffic ([pricing](https://www.aurinko.io/pricing/)).
- **EmailEngine**: $1,450 or &euro;1,200 a year for unlimited mailboxes, on your own infrastructure ([home page](https://emailengine.app/)).
- **Gmail API**: free within quota (6,000 units per user per minute, 1.2 million per project). Google says charges for usage above its thresholds start later in 2026 ([usage limits](https://developers.google.com/workspace/gmail/api/reference/quota)).
- **Workwae**: a Free plan, and paid plans you buy yourself in the console, through Stripe. A plan is limits on connected accounts, daily sends, API rate, webhook endpoints and storage, plus a base fee and metered usage; AI classifications and drafts are billed as overage past what the plan includes. The console shows the prices before you subscribe ([Pricing](https://workwae.com/pricing)).

## Side by side.

| Product | Scoped credentials | Draft without send | MCP server |
| --- | --- | --- | --- |
| Workwae | Key scopes and account limits | Yes; send policy on top | Hosted |
| Nylas | IAM principals per grant, workspace or app | Confirmation step for sends | Hosted, 38 tools |
| Unipile | Not documented | Not documented | For coding agents |
| Aurinko | Scopes per user token | Unclear: the draft scope includes send | Not documented |
| EmailEngine | Scopes, grants, binding, IP limits | Yes, through grants | Self-hosted, beta |
| Gmail API | OAuth scopes | No: `gmail.compose` includes send | Preview, no send tool |
| Microsoft Graph | Permissions; RBAC for app-only | Yes: `Mail.ReadWrite` | Preview (Agent 365) |

| Product | Change delivery | Pricing unit | Providers |
| --- | --- | --- | --- |
| Workwae | Signed webhooks, change feed | Base fee plus metered usage; Free plan | Gmail, Microsoft 365, IMAP |
| Nylas | Signed webhooks, Pub/Sub, SNS | Per account, from free | Gmail, Microsoft, IMAP and more |
| Unipile | Webhooks | Per account, no usage fees | Mail plus LinkedIn, WhatsApp |
| Aurinko | Webhooks API | Per account, by data | Gmail, Microsoft, IMAP |
| EmailEngine | Webhooks and routes | Flat yearly license | Gmail, Microsoft, IMAP |
| Gmail API | Pub/Sub cursor; watch renewed within 7 days | Free within quota | Gmail only |
| Microsoft Graph | Change notifications, delta | Not stated on pages read | Microsoft only |

## Which one fits.

- **One provider, and you will run the Google or Microsoft integration anyway.** Go native. Graph lets you separate drafting from sending by permission. Gmail does not, and reading mail brings verification and an annual assessment.
- **Several providers, real users’ mailboxes, send kept apart from drafting.** Workwae, Nylas and EmailEngine all do this. Nylas has the longer record and published pricing; EmailEngine runs on your servers; Workwae is in early access.
- **The agent needs its own address.** Nylas sells Agent Accounts for that. Workwae connects mailboxes that already exist.
- **The agent also works LinkedIn or WhatsApp.** Unipile covers those channels next to mail.
- **Per-account cost matters most.** Compare the marginal account: Aurinko is $1 to $2, Nylas $1.75 to $2.25 beyond the included ones, Unipile &euro;5. EmailEngine’s flat fee undercuts all of them at scale, before your hosting costs.

The vendor-by-vendor pages go further: [Nylas](https://workwae.com/alternatives/nylas), [Unipile](https://workwae.com/alternatives/unipile), [Aurinko](https://workwae.com/alternatives/aurinko) and [EmailEngine](https://workwae.com/alternatives/emailengine).

## Limits.

- **Prices are not on this site.** Workwae has a Free plan and a self-serve checkout, but the prices show in the console, once you have a workspace.
- **No SOC 2 report and one region.** SOC 2 is planned, not started, and data is hosted in the United States only. Nylas documents SOC 2 Type II and a European region.
- **Google verification.** Workwae’s own Google app has not completed the security assessment. If you need a verified app, bring your own and complete verification yourself.
- **An agent mailbox of its own.** Workwae has no equivalent of Nylas Agent Accounts.
- **Prompt injection is not solved by scopes.** Workwae fences third-party text as untrusted data, which helps the model and is not a guarantee. Keep confirmation on.
- **Alpha SDKs.** `@workwae/sdk` is at 0.1.0-alpha and `workwae` at 0.1.0a2.

[AI email agents](https://workwae.com/use-cases/ai-agents) shows the draft-only agent loop in code, and [the MCP guide](https://docs.workwae.com/guides/mcp) covers connecting each client.

## More from the blog.

### [Sending email from your users’ mailboxes: limits, bounces, tracking and merges.](https://workwae.com/blog/sending-email-from-your-users-mailboxes)

November 4, 2026 · 15 min read

Daily limits, authentication, the 5,000-a-day rules, bounces, suppression, validation, tracking, merges and retries.

Tags: Sending, Gmail, Microsoft Graph

### [Email and calendar webhooks you can trust.](https://workwae.com/blog/email-webhooks-you-can-trust)

October 26, 2026 · 7 min read

Signatures, duplicates, ordering, retries, replay and secret rotation for mail and calendar webhooks.

Tags: Webhooks, Sync and push

### [Sending mail as your users without breaking their mailbox.](https://workwae.com/blog/sending-mail-as-your-users)

October 19, 2026 · 6 min read

Sent copies, Message-IDs, In-Reply-To, References, Gmail threadId rules and drafts across SMTP, Gmail and Graph.

Tags: Sending, Gmail, Microsoft Graph
