What problem does it solve? Adding transactional email to an application requires navigating Cloudflare Email Service setup, domain onboarding, binding configuration, and deliverability rules, and outdated knowledge of this 2025-launched product leads to common integration mistakes. ## Core Features & Use Cases - Email Sending: Send emails from Cloudflare Workers via the send_email binding, from external apps via the REST API, or from AI agents using the Agents SDK onEmail() and replyToEmail() methods. - Email Routing: Receive and process inbound emails with a Worker's email() handler, including forwarding, replying, rejecting, and MIME parsing with postal-mime. - Setup & Deliverability: Onboard domains with wrangler CLI or MCP tools, configure SPF/DKIM/DMARC, manage suppression lists, and monitor delivery with GraphQL analytics. - Use Case: A developer building a support inbox stores incoming emails in a Durable Object, lets a human review drafts, and sends threaded replies later via the send_email binding with proper In-Reply-To headers. ## Quick Start Ask the agent to add email sending to your Cloudflare Worker using the send_email binding and verify the sending domain is onboarded.