Cloudflare Email Service: now in public beta. Ready for your agents

Email is the most accessible interface in the world. It is ubiquitous. There’s no need for a custom chat application, no custom SDK for each channel. Everyone already has an email address, which means everyone can already interact with your application or agent. And your agent can interact with anyone.

Cloudflare Email Service is now in public beta, allowing any application and any agent to send emails. With Email Routing, you can receive email to your application or agent. With Email Sending, you can reply to emails or send outbounds to notify your users when your agents are done doing work.

Email Sending graduates from private beta to public beta today. You can now send transactional emails directly from Workers with a native Workers binding – no API keys, no secrets management. When you add your domain to Email Service, Cloudflare configures SPF, DKIM, and DMARC records automatically.

The Agents SDK for building agents on Cloudflare already has a first-class onEmail hook for receiving and processing inbound email. With Email Sending, your agent can receive a message, spend an hour processing data, check three other systems, and then reply with a complete answer. It can operate independently.

Key technical advantages include:

• Each agent gets its own identity from a single domain.
• State persists across emails using Durable Objects.
• Secure reply routing is built in using HMAC-SHA256 signatures.

Cloudflare is also shipping integrations like the Email MCP server and Wrangler CLI email commands to make Email Service accessible to any agent, regardless of where it runs.