Blog
Essays on email for AI agents - the arguments behind owned mailboxes, EU data residency, and where the category is going.
Latest
The Case for EU Data Residency in Agent Infrastructure
For EU and privacy-first teams, where your agent's email lives - and which legal jurisdiction governs the company that holds it - is…
ReadThe Real Cost of the Gmail API for Agents (CASA)
**Using the Gmail API to let an agent read or receive a person's mail is expensive in time and money, because those actions use Google's…
ReadYou Can't Cleanly Open a Google Account for Your AI Agent - What to Do Instead
There is no compliant, durable way to give an AI agent its own Gmail account. Consumer signups are gated by CAPTCHA and risk-based phone…
ReadIMAP Is Legacy; JSON-Native Email Is the Future
IMAP works, but it is the wrong contract for an AI agent. It's a stateful, connection-oriented protocol from 1986 built for a person's mail…
ReadWhy Agents Need Their Own Mailbox, Not Access to Yours
An AI agent should have its own mailbox - an address and credential that belong to the agent's operator - rather than OAuth-delegated…
ReadPrompt Injection via Inbound Email - and How We Think About It
**Prompt injection via email is a real, largely unsolved security problem: because any stranger can send a message, an inbound email is…
ReadThe State of Email for Agents 2026
**In 2026, "email for agents" became a real, funded category. The consensus framing across investors and analysts is that the opportunity…
Read
Give your agent a real mailbox
Two-way email over REST and a native MCP server - EU-resident by default.
EU data residencyPer-customer encryptionNative MCP