Cloudflare Email Service: Email Built for AI Agents
Cloudflare put Email Sending into public beta on April 16, 2026, during Agents Week, and paired it with the Email Routing service it has offered free for years. Together they are Cloudflare Email Service, and the pitch is narrower and more interesting than “another transactional email API”: email as a first-class way for an AI agent to receive work and report back.
That framing matters, because the hard part of agent email was never the sending.
What actually ships
Outbound runs through a Workers binding. You call env.EMAIL.send() with no API key to store, rotate, or leak, because the credential is the binding itself. If you would rather not bind, there is a REST API with official SDKs for Node, Python, and Go, plus authenticated SMTP at smtps://smtp.mx.cloudflare.net:465 for systems that only speak SMTP.
Inbound runs through Email Routing. A routing rule hands the message to your Worker, where you parse sender, recipients, headers, and body and decide what happens. Routing is address-based, so support@yourdomain.com can land on one agent and billing@ on another.
The agent hook is where the Agents SDK earns its place. An agent implements async onEmail(email: AgentEmail) and receives the parsed message directly. Because Cloudflare’s agents are backed by durable state, the conversation persists between messages. The agent that reads the third reply in a thread is the same agent, with the same memory, that read the first.
Reply routing is handled by putting a stable identifier into the reply address or headers, so a response three days later reaches the right agent instance instead of a generic handler that has to guess. Cloudflare signs those identifiers to stop anyone forging their way into someone else’s agent session, which is the failure mode most homegrown implementations discover the hard way.
Cloudflare also open-sourced Agentic Inbox, a full reference email client built on the stack: Email Routing for inbound, Email Sending for outbound, Workers AI for classification, R2 for attachments, and the Agents SDK for the stateful logic. It is the most useful part of the launch if you are trying to decide whether the primitives compose into something real.
What it costs
Email Sending includes 3,000 messages per account per month, then $0.35 per 1,000. It requires the Workers Paid plan, which starts at $5 per month and covers Workers, Durable Objects, KV, and the rest of the runtime. Messages rejected at the API boundary or blocked by a suppression list do not draw down the quota.
Email Routing is unlimited on both Free and Paid plans, and sending to destination addresses you have verified on your own account is free everywhere, which makes the “agent emails me” pattern free to build and test.
Because it is still in beta, treat the per-message rate as provisional. Cloudflare has said it will update documentation before changing what it charges, but a beta price is a beta price.
Who this is actually for
This is developer infrastructure. You need a Cloudflare account, a domain on Cloudflare, and someone comfortable writing and deploying a Worker. In exchange you get the cheapest credible floor in the category and no separate email vendor in the stack.
It fits well when you are already on Cloudflare, when your agent needs both directions of email rather than just outbound notifications, and when per-message economics matter at volume. It fits badly when you want an inbox that works this afternoon without deploying anything.
The one real constraint is gravity. The agent hook, the durable state, and the binding all assume you are running on Workers in TypeScript. That is a reasonable assumption if you already live there and a significant commitment if you do not.
If you want an agent with an email address and no deployment step at all, Carly arrives with one attached: free Zapier-style workflows, with AI agents from $35/month. Running it from your own code, provisioning agents per tenant, or embedding it in your product is available. Book a call with the team and we will scope it.
How it compares to the dedicated agent-inbox vendors
A small category grew up specifically around giving agents mailboxes, and Cloudflare has now undercut it on price while asking for more assembly.
The dedicated providers hand you threading, reply matching, label state, attachment storage, and loop prevention as solved problems. Cloudflare hands you transport, routing, durable state, and a reference app, and expects you to assemble the rest. Given that Email Routing is free and 3,000 sends are included, the trade is engineering time against a bill that is close to zero.
That calculus flips fast if threading is your actual problem rather than delivery. Email APIs for AI agents maps each build pattern to what it genuinely requires, and the AgentMail alternatives rundown covers the field Cloudflare just walked into.
Worth being clear about which problem you have first, because “AI agent email address” means two unrelated things depending on who is asking. The two meanings are worth ten minutes before you pick a vendor.
FAQ
Is Cloudflare Email Service free?
Email Routing is free on both plans. Email Sending includes 3,000 messages per account per month and then charges $0.35 per 1,000, and it requires the Workers Paid plan starting at $5 per month. Sending to destination addresses verified on your own account is free on all plans.
Is it out of beta?
Email Sending entered public beta in April 2026 and remains in beta. Email Routing has been generally available for years. Pricing on the sending side should be treated as provisional.
Can I use it without writing a Worker?
Partly. The REST API and authenticated SMTP let you send from anywhere, including Python or Go. The inbound side and the agent onEmail hook require a Worker, so full two-way agent email means deploying one.
Does it handle threading and reply matching?
Not as a finished feature. It gives you the pieces, stable reply identifiers and durable per-agent state, and the Agentic Inbox reference app shows how to assemble threading from them. Dedicated agent-inbox vendors ship that already built.
What language do I have to write it in?
The Agents SDK and the onEmail hook are TypeScript on Workers. Sending is language-agnostic through the REST API, with official SDKs for Node, Python, and Go.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
