Cloudflare just shipped something agents have needed: real email. Their Email Service entered public beta today, giving AI agents bidirectional email with built-in authentication (SPF, DKIM, DMARC) and state persistence via Durable Objects. The release, announced by Thomas Gauvin and Eric Falcão as part of Cloudflare's 'Agents Week,' includes an Agents SDK with an onEmail hook, an MCP server for Model Context Protocol integration, and an open-source Agentic Inbox reference app. The pitch is straightforward. Email is universal, so your agents should speak it natively instead of requiring custom chat apps or channel-specific SDKs. Agents receive messages through Email Routing, process them in Workers, and reply via Email Sending. no API keys. State persists across conversations because agents run on Durable Objects, meaning your support agent remembers context without a separate database. Reply routing uses HMAC-SHA256 signing to prevent header forgery attacks. Most email-for-agents solutions have apparently ignored this problem. A support agent can receive a message, spend an hour processing data across three systems, and reply with a complete answer. That's the core distinction Cloudflare draws between chatbots (synchronous, instant) and agents (asynchronous, stateful, operating on their own timeline). Hacker News commenters aren't all sold. Several pointed out that traditional automation handles most highlighted use cases (CI notifications, shipping confirmations, support tickets) without needing an 'agent' wrapper. Others raised legitimate concerns about email as a channel: SMTP's near-zero sending cost invites spam, and inbox placement increasingly depends on goodwill from Google and Microsoft, who control the dominant consumer providers. If those gatekeepers tighten filters or move toward pay-to-play delivery, any transactional email service faces an uphill battle. Cloudflare's actual competition is Zapier and Make, the automation platforms that currently glue email workflows together. The difference is raw, programmatic control over the email transport layer with compute at the edge, rather than pre-built integration blocks. Whether developers want that control or would rather stick with simpler automation tools remains an open question. For teams already building agents on Cloudflare's platform, having email as a native capability instead of an external API dependency is a genuine advantage.