Cloudflare Email Service: now in public beta, ready for agents

Cloudflare has moved Email Service to public beta, accelerating the trend of using email as the default interface for agents.

The core is bidirectional email infrastructure.

• Email Sending is now in public beta, letting you send mail directly via a Workers binding.
• You can send with env.EMAIL.send() without managing API keys, and Cloudflare also provides a REST API and TypeScript / Python / Go SDKs.
• When you register a domain, SPF / DKIM / DMARC are configured automatically to align deliverability and authentication.
• Combined with the existing Email Routing, you can now do receive → process → reply entirely within Cloudflare.

The Agents SDK has also been strengthened around email.

• The onEmail hook lets you receive and process emails, work asynchronously if needed, and then send a reply.
• As in the example, a support agent can receive an email, save state, trigger a background task, and then reply.
• This supports an agent pattern that works over time, rather than a chatbot that only responds instantly.

The internal mechanics are also specific.

• An address-based resolver routes addresses like [email protected] to a specific agent instance.
• Sub-addressing is also supported, enabling namespace separation.
• Agent state is kept on Durable Objects, so email conversation context persists.
• Reply routing is protected with HMAC-SHA256, preventing attacks that forge headers to redirect to a different agent instance.

Cloudflare also shipped surrounding tools so email can be used anywhere.

• The email API can be called from the Cloudflare MCP server.
• Email commands have been added to the Wrangler CLI, so agents in bash environments can send mail with low context overhead.
• Skills for the email service have also been released, covering setup, sending, inbound processing, and deliverability best practices.

Finally, Cloudflare released an open-source reference app called Agentic Inbox.

• It includes conversation threading, email rendering, attachment storage, and automatic replies.
• It combines Workers AI, R2, and the Agents SDK, serving as an example for building real email apps and agents.
• It offers a reusable starting point for the inbound-classify-reply pipeline that teams have repeatedly built from scratch.