If your agents already run on Cloudflare Workers, this is the cheapest way to give them email: inbound is unmetered and replies happen in the same code. It replaces wiring a separate sending API and webhook server. Everyone else should wait: sending is in beta and each message tops out at 50 recipients.
What changed
Cloudflare Email Service is Cloudflare's email product for developers, joining Email Routing for inbound mail with Email Sending, in public beta since 16 April 2026. It sends from Workers, a REST API or SMTP, and its Agents SDK integration gives an agent an onEmail hook to receive, process and reply to messages without a separate server.
About Cloudflare Email Service
Cloudflare Email Service combines two things Cloudflare built separately: Email Routing, which receives mail for your domain and forwards it or hands it to a Worker, and Email Sending, which went into public beta on 16 April 2026. Sending works through a Workers binding, a REST API or, since June 2026, authenticated SMTP, and the service is billed as part of a Workers plan rather than as a separate subscription.
For agent builders the draw is the Agents SDK. An agent built on Cloudflare gets an onEmail hook that receives a message, processes it and replies, and Cloudflare removed earlier reply restrictions in March 2025 so that Workers could answer in threads for exactly this kind of automation. Inbound routing has no message cap on either Workers plan, and an Email MCP server in Cloudflare's MCP repository, plus Wrangler CLI email commands, let an agent running somewhere else send through the same account.
What you do not get is storage. There is no inbox: Cloudflare's own examples save incoming mail to Workers KV and process it with Queues, and the activity log preview keeps sent messages for about a week. That makes it a strong base for a team that already writes Workers and wants to own its data, and a poor fit for anyone who wants to open a thread in a dashboard. If you want threads kept for you, AgentMail does it as its whole product, and Resend does it beside its sender. Inside AWS, the comparable build-it-yourself pipe is Amazon SES.
New sending accounts start with a conservative daily quota that rises with reputation, every message is capped at 50 recipients and 25 MiB, and sends are DKIM- and ARC-signed automatically. Our guide to AI agent builders covers the frameworks that can call it, including Mastra.
It is one of six providers in Hokai's email services category; Postmark and SendGrid remain the mature managed senders. Agents that hold a phone number as well as an address are covered in our AgentPhone explainer, and the OpenClaw playbook shows a personal agent taking messages from several channels.
Plans and pricing
From Cloudflare's docs, checked 6 November 2026. Workers Free: inbound routing unlimited, outbound sending not available except to verified destination addresses. Workers Paid (minimum $5/mo per account for the Workers plan): 3,000 outbound emails included per month, then $0.35 per 1,000; inbound unlimited.
Hard bounces count toward the quota; sends rejected at the API or blocked by the suppression list do not. Workers that process routed mail are billed at normal Workers rates.
Server plans
| Plan | Price |
|---|---|
| Workers Free Cloud · Inbound routing only; no sending to arbitrary recipients · Global | $0/mo |
| Workers Paid Cloud · Monthly sending allowance included, metered beyond it; Workers plan minimum · Global | $5/mo |
Key Features
- Agents SDK onEmail hook: Agents built on Cloudflare receive, process and reply to mail through a native hook, without a separate webhook server.
- Email Routing: Routes mail for your domain to verified addresses or to a Worker, with up to 200 routing rules per domain and subaddressing support.
- Three ways to send: A Workers binding (env.EMAIL.send()), a REST API and authenticated SMTP all feed the same delivery pipeline and limits.
- Suppression lists: Account-wide and per-sending-domain suppression entries stop sends to bad addresses, with bulk import of up to 1,000 entries per request.
- Event subscriptions: Sending events can be delivered to Cloudflare Queues so an agent reacts to bounces and deliveries asynchronously.
Strengths
- Inbound mail costs nothing to route on either Workers plan, the only provider here that does not meter received messages.
- Agents written with Cloudflare's Agents SDK handle mail in the same code and runtime as everything else they do.
- Sending is priced like infrastructure, so an agent that sends a few thousand messages pays little beyond the Workers plan.
Weaknesses
- Email Sending was still labelled beta in Cloudflare's documentation on 6 November 2026.
- There is no stored inbox or threading; you keep messages yourself in KV, D1 or another store.
- New accounts start on a low daily sending quota that only rises as sending reputation builds.
Frequently Asked Questions
What does Cloudflare Email Service actually cost?
Sending needs the Workers Paid plan, which has a $5 monthly minimum, and includes 3,000 outbound emails a month before charging $0.35 per 1,000, per Cloudflare's pricing docs updated 9 June 2026. Inbound routing is unlimited on both Workers plans. Any Worker you run to process routed mail is billed at normal Workers rates, and storage is whatever you choose.
Can you use Cloudflare Email Service without paying?
Partly. On Workers Free you can route unlimited inbound mail to verified addresses or a Worker, and send to verified destination addresses in your own account, but you cannot send to arbitrary recipients. That is enough for an agent that only listens, or one that only reports back to you.
Which services compete with Cloudflare Email Service for agents?
Amazon SES is the closest match: a metered pipe where you build storage yourself, but mature and outside beta. AgentMail and Resend sell the layer Cloudflare leaves out, with stored threads an agent can read. Postmark and SendGrid are better if your agent mostly sends.
How does Cloudflare Email Service compare to Amazon SES in 2026?
Both are build-it-yourself pipes, but Cloudflare does not charge for inbound and wires mail into the Agents SDK, while SES meters both directions and drops inbound into S3, SNS or Lambda. SES sending is not in beta; Cloudflare's sending was still in beta in November 2026. Choose by where your agent code already runs.
Is Cloudflare Email Service production-ready?
Inbound routing is the older, established half, but Email Sending entered public beta in April 2026 and authenticated SMTP in June 2026, and neither was marked generally available in the docs on 6 November 2026. New accounts also begin on a conservative daily quota. It is reasonable for internal agents and side projects; for customer-facing mail at volume, keep a fallback sender ready.
Top Alternatives
- Amazon SES: Pick Cloudflare if your agents run on Workers; pick Amazon SES if they run on AWS and you want a mature, non-beta sender.
- AgentMail: Pick Cloudflare to own storage and pay infrastructure prices; pick AgentMail to get stored inboxes with no plumbing.
- Resend: Pick Cloudflare for free inbound and Workers-native agents; pick Resend for a dashboard, templates and threaded inboxes.
- Postmark: Pick Cloudflare for cheap agent mail on Workers; pick Postmark for proven transactional delivery and long logs.
Hokai guides that mention Cloudflare Email Service
- Best Email APIs for AI Agents in 2026: Inbox or Webhook?: Six email APIs for AI agents compared: which give an agent a real inbox, what 10,000 emails each way cost, free-plan catches, retention and safety controls.