What problem does it solve? Integrating transactional email into applications requires navigating Cloudflare Email Service's evolving APIs, domain onboarding, DNS authentication, and subtle differences between the Workers binding and REST API, where mistakes cause silent delivery failures. ## Core Features & Use Cases - Email Sending: Send transactional emails from 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. - Inbound Email Routing: Receive, parse, forward, reply to, or reject incoming emails with a Worker's email() handler and postal-mime parsing, including store-and-reply-later patterns with Durable Objects. - Deliverability Management: Configure SPF/DKIM/DMARC, monitor bounces and suppression lists, and query email analytics through the GraphQL API. - Use Case: Add a welcome email to a Cloudflare Worker by enabling the domain with wrangler email sending enable, adding the send_email binding, and calling env.EMAIL.send() with verified sender addresses. ## Quick Start Ask the agent to add email sending to your Cloudflare Worker using the send_email binding with a verified domain.