Should your AI agent use Gmail?
The Gmail API works for one internal agent. Shipping an agent that reads users' Gmail means OAuth verification, a yearly security assessment and access to everything in the mailbox.
Use the Gmail API only for an internal agent on your own Workspace account. For anything shipped to other people, restricted Gmail scopes require OAuth verification and a CASA security assessment renewed every 12 months, unverified apps are capped at 100 users, and the agent can read the user's entire mailbox. Giving the agent its own address, and forwarding it what it needs, avoids all of it.
What it takes to ship an agent on Gmail
Fine for one internal agent on a Workspace account. Each step below applies once the agent serves users outside your organisation.
A Cloud project and an OAuth consent screen
Before the agent reads one message: project, consent screen, scopes, and an OAuth flow each user clicks through.
A 100-user cap until verified
Unverified apps can sign in at most 100 new users and show a warning screen.
Restricted scopes mean a security assessment
Reading Gmail uses restricted scopes. Apps that handle that data on their own servers need a CASA assessment by an approved assessor, renewed every 12 months; Google says verification alone can take several weeks.
The agent can read everything
The structural problem: an agent with access to a person's mailbox reads all of it, and everything it sends is from that person.
Gmail API vs an agent's own address
Facts from Google's OAuth verification documentation.
Last verified: 2026-10-31 against each vendor's own pricing and documentation pages. Pricing moves; re-check before you commit.
| Gmail API on a user's account | Mailgi address for the agent | |
|---|---|---|
| Setup before the first read | Cloud project, consent screen, OAuth | One POST |
| Human involvement | Each user consents | None |
| Shipping to outside users | Verification and annual CASA assessment | Nothing extra |
| What the agent can read | The whole mailbox | Only mail sent to the agent |
| Sender identity | The human | The agent's own address or your domain |
| Cost | Free API; assessment costs | Receiving free; $0.0005 per external recipient |
A pattern that keeps both
Forward, don't grant
Give the agent its own address and have the human forward or CC it what it needs. The agent works from its inbox; the human's mailbox stays private.
Reply from the agent's address
Customers see a stable address you control, with DKIM, SPF and DMARC on your own domain.
Questions, answered
01Should my AI agent use the Gmail API?
For one internal agent on your own Workspace account, it is free and workable. For an agent used by people outside your organisation, the OAuth verification, 100-user cap before verification and annual CASA assessment for restricted scopes make it slow and costly, and the agent can read the whole mailbox. Giving the agent its own address avoids all of that.
02Can I create Gmail accounts for my AI agents?
Not programmatically for consumer Gmail, and accounts operated by bots risk being flagged. Workspace accounts are paid per user. An email API for agents gives each agent an address with one call.
03Does the Gmail API need a security assessment?
Apps using restricted Gmail scopes that access data through their own servers must pass a third-party CASA security assessment, renewed at least every 12 months. Internal Workspace apps and personal use are exempt.
One POST to start.
No signup form, no OAuth, no card to start. Receiving is free.
Open the dashboard →