Sairaph Mail vs the Gmail API: an honest comparison (2026)

The distinction that decides everything

The Gmail API assumes there is already a Google account, belonging to a human, and that you are asking to act on that person's behalf. That framing drives every cost below. If you only want *sending* from a personal Google account, the gmail.send scope is a sensitive scope: it needs OAuth app verification but no third-party audit (Google Cloud, scope levels). But for an agent the value is almost always in *receiving* - reading a one-time code, catching a reply, triaging inbound. Reading or receiving a person's Gmail uses Google's restricted scopes (including https://mail.google.com/, which also covers IMAP, SMTP, and POP), and restricted scopes are what trigger the heavy path.

Sairaph Mail sidesteps the framing entirely. There is no human account to borrow. You provision a mailbox, get a scoped API key from the dashboard, and the agent sends and reads over REST (/api/v1) or MCP (/mcp/v1/mcp). Software owning the mailbox is the intended use, not an exception Google has to audit.

At a glance

Setup complexity, side by side

Gmail API, production path (reading mail):

1. Create a Google Cloud project and configure the OAuth consent screen.
2. Verify your brand and the consent screen.
3. Justify each restricted scope and show why a narrower one will not do.
4. Provide a demo video of the OAuth flow and your data use.
5. Pass a CASA assessment by an authorized third-party lab, producing a Letter of Validation.
6. Re-do that validation every 12 months to keep access (Google Cloud, OAuth verification FAQ).

Add token management on top: refresh tokens expire, consent can be revoked, and "Testing" mode caps you at 100 users with a 7-day refresh-token expiry until you are fully verified. Running many inboxes cleanly means service accounts with domain-wide delegation, which require a paid Workspace and a super-admin, not a free @gmail.com.

Sairaph Mail:

1. Sign up and provision a mailbox (instant on a Sairaph brand domain, or bring a custom domain by publishing the DNS records the dashboard shows you).
2. Issue a scoped API key from the dashboard and give it to the agent.

That is the whole setup. No consent screen, no restricted-scope justification, no demo video, no CASA lab, and nothing to re-verify a year later.

The real cost

The load-bearing fact about the Gmail API is not a license fee, it is the annual compliance treadmill attached to reading mail. What is firmly documented by Google: restricted scopes require the CASA assessment and annual re-verification, for as long as your agent reads mail. What is reported but variable: industry write-ups commonly cite an annual CASA cost in roughly the $15,000 to $75,000 per year range depending on tier and provider. That range is aggregator- and vendor-sourced, not an official Google price list, so treat it as directional and get a current quote before you budget on it. We break down the detail in the real cost of the Gmail API for agents. Either way, the *time* cost is certain: weeks of verification work plus ongoing token and consent engineering.

Sairaph Mail's cost is the plan price on the pricing page, and it is the same full platform on every tier. There is no audit line item, because there is no audited scope to keep.

Where the Gmail API is the better choice

The Gmail API is the right tool, and often the *only* tool, when the job is genuinely about a human's own Google mailbox:

• You need to act inside a real person's existing Gmail or Workspace inbox with Google's official, sanctioned API - for example a product that triages a user's own Gmail with their consent, or that reads and sends as them. Sairaph Mail gives an agent a *separate* owned mailbox; it does not operate a user's Gmail through Google's first-party API. (Sairaph can *connect* an existing Gmail as an external mailbox over IMAP and SMTP with an app password, but that is a lighter, provider-limited path, not Google's Gmail API with delegated OAuth scopes.)
• Org-wide Google Workspace automation. If you are automating across the inboxes of an existing Workspace organization via domain-wide delegation, that lives natively in Google's ecosystem and belongs on the Gmail API.
• Deep Gmail-native features. Gmail labels, filters, and the specifics of Google's threading model are Google's own surface. If your value is tied to those, use the API that exposes them.

If any of these describe you, the CASA treadmill is a cost of doing business in Google's ecosystem, and the Gmail API is where you should be.

Where Sairaph Mail is the better choice

• The agent owns the inbox. No borrowed human account, no OAuth grant to maintain, no consent that can be revoked out from under the agent. A provisioned mailbox with a scoped key it holds.
• Reading mail is not gated behind an annual audit. Receiving is the whole point for most agents, and it is included from the first call, with no restricted-scope justification and no CASA re-validation each year.
• A first-party MCP server. Register /mcp/v1/mcp and the mailbox's actions appear as tools in an MCP-capable runtime, authed with the same sm_live_… key. See email for AI agents.
• EU residency by default. Storage and processing are EU-hosted (OVHcloud + an Amazon SES relay in eu-west-1) under an EU-incorporated company. See security.

EU honesty, stated plainly: email is store-and-forward, so a message you send travels to the recipient's server wherever that is, and the SES relay leg runs on AWS. We do not claim "your email never leaves the EU."

How to decide

• Operating a real human's existing Gmail or Workspace inbox, as a Google-sanctioned integration? The Gmail API.
• Giving an agent its own owned mailbox it sends from and reads back from, without a Google account or an annual security audit? Sairaph Mail.
• Not sure it is worth borrowing a human's inbox at all? Read why you cannot cleanly open a Google account for an agent first - the upstream problem often makes the decision for you.

The real surface to evaluate Sairaph Mail on: REST at /api/v1, the MCP server at /mcp/v1/mcp, and the published API reference at /docs.

Related

• Compare hub · The real cost of the Gmail API (CASA)
• You cannot cleanly open a Google account for your agent
• Email for AI agents
• Pricing · Security