On 8 October Google said its Gemini coworker agents get their own Workspace account, email address included. It is the loudest sign yet of something the industry settled this year: an agent that does real work should have an address of its own, not borrow yours.
Google's own wording is plain. A coworker agent "receives its own Workspace account, including an email address, calendar, Drive, and presence in your company directory." Elsewhere in the same post: coworker agents have "dedicated identities including their own @agents.company.com emails." TechCrunch's report adds that the agent writes an audit trail attributed to itself rather than to a person, and that Google is starting with businesses.
Google is not alone. Zoho opened early access to AgentInbox on 24 September, promising each agent "its own mailbox, its own credentials, and a complete audit trail." Cloudflare put its Email Service into public beta in April with an Email MCP server for agents. AgentMail, which builds nothing but inboxes for agents, raised a $6M seed in March. Four very different companies landed on the same idea in the space of one year.
OpenAI's dots, the always-on agents now rolling out in ChatGPT, have their own cloud computer and browser. For email, though, OpenAI's docs point you to a plugin such as Gmail, so a dot works inside your inbox unless you give it one of its own. We show how in ChatGPT dots and email.
What every new colleague gets on day one
Think about a new hire's first morning. Before anyone explains the job, they are handed four things. A name people can recognise. An address that mail can reach. A login that IT can switch off. And a manager who can see what they are doing. None of that is about talent. It is about being someone the organisation can trust, reach and account for.
Agents were missing all four. The usual shortcut was to connect the agent to a person's Gmail or Outlook with OAuth. That gives it an address, but the wrong one. Every email it sends looks like you wrote it, it can read everything you ever received, and switching it off means revoking access to your own inbox.
A name. An address like support@ or invoices@ tells the person on the other end what they are talking to. Google's @agents.company.com goes one step further: the domain itself says "this is an agent".
An address mail can reach. An agent that can send but never read the answer is half an employee. Replies, verification codes and forwarded invoices need somewhere to land that the agent, not a person, owns.
A login you can switch off. A credential that reaches one mailbox can be revoked without touching anyone else's. That is the whole point of the "own credentials" line in Zoho's post.
A manager who can see the work. When an agent acts under its own identity, its trail is its own. Nobody has to dig through a person's Sent folder to find out what the agent promised a customer.
An agent that borrows your inbox is acting as you. An agent with its own address is acting as itself, and that is the version you can audit.
Getting the same thing without Google Workspace
Google's version lives inside Workspace and Gemini. If your team runs on something else, or you are building your own agents in code, you need the address without the suite. That is the gap the agent inbox services fill, and it is what we built Faivelo Agents for.
The shape mirrors Google's. Put your agents on a subdomain such as agents.yourcompany.com, so people can tell at a glance which mail came from software. Give each agent its own inbox, and give it an agent key that reaches only that inbox. It can never read your other mailboxes, touch billing or add domains. Revoke the key and access stops at once.
The agent drives its inbox over the REST API, webhooks or the hosted MCP server, so Claude, Cursor or your own code can send, read and reply. You read along in the Inboxes console and see everything it sends and receives. For a step-by-step setup, see how to give an AI agent an email address.
| Faivelo Agents plan | Price | Agent inboxes | Emails a month | Your own domains |
|---|---|---|---|---|
| Free | $0 | 3 | 3,000 | A free address on fvlmail.com |
| Developer | $15 a month | 50 | 20,000 | 10 |
| Scale | $150 a month | 500 | 300,000 | 50 |
Emails count sent plus received. The REST API, hosted MCP server and message webhooks come with every plan, Free included.
What changes once agents have addresses
Once an agent has an identity, the questions you ask about it get simpler. Who sent this? The agent, and its address says so. What did it promise? Look in its inbox. Can we stop it? Revoke one key. These are the same questions you would ask about any colleague, and now they have the same answers.
It also changes what email is for. Inboxes used to be where people talked to people. Increasingly they are where people, services and agents meet. A supplier replies to a purchasing agent, a SaaS tool sends a sign-up code, a colleague forwards a thread and asks the agent to handle it. We wrote more about that shift in what agentic email means.
If you are weighing providers, our side-by-side of agent inbox services compares AgentMail, Zoho, Cloudflare, Google and Faivelo on price, domains and how a person keeps watch.
Give your agent an address of its own
Start on the free plan with three agent inboxes, or put them on your own domain from $15 a month. The API, MCP and webhooks are on every plan, and you see everything your agents send.