What problem does it solve? Integrating the Resend email API correctly involves many non-obvious pitfalls — idempotency keys for safe retries, webhook signature verification, template variable syntax, and domain DNS setup — and mistakes cause duplicate sends, bounced emails, or spoofed webhook events. ## Core Features & Use Cases - Transactional Email Sending: Send single or batch emails with idempotency keys, attachments, scheduling, and templates across 8+ SDK languages (Node.js, Python, Go, Ruby, PHP, Rust, Java, .NET). - Inbound Email & Webhooks: Receive emails via MX records or Resend-managed domains, verify Svix webhook signatures, and retrieve bodies and attachments through the Receiving API. - Audience & Campaign Management: Manage domains, contacts, segments, topics, broadcasts, automations, events, API keys, and request logs. - Use Case: Build an order-confirmation flow where your app sends a templated email with an idempotency key on checkout, tracks delivery via verified webhooks, and auto-removes hard-bounced addresses. ## Quick Start Ask the AI to send a transactional email with Resend using an idempotency key and proper error checking.