Designing for Agents — Zeno Rocha, Resend
Summary
This deep dive explores the infrastructure and strategic decisions behind building a modern email platform (Resend). The discussion highlights the shift from traditional, IP-based deliverability models to complex, domain-based reputation management. Key architectural takeaways include adopting an API-first, developer-centric approach, building multi-channel communication platforms, and integrating advanced agent capabilities via the Messaging Connector Protocol (MCP). The conversation also addresses the challenges of scaling support, optimizing for AI-driven search (AEO), and managing the technical debt inherent in complex, regulated industries like email.
Key takeaways
-
Domain-Based Reputation is Key
22:08
Email reputation has shifted from being primarily IP-based to being domain-based. To mitigate risk, platforms must encourage users to segment communication using multiple subdomains (e.g., `transactions.resend.com` vs. `marketing.resend.com`) to prevent a single abusive sender from damaging the entire domain's reputation.
-
The Necessity of API-First Design
18:41
The platform philosophy is to be 'formless' and API-first, ensuring that the product can support any future use case without needing to rebuild the core infrastructure. This approach is crucial for integrating with modern development environments and agents.
-
Agent Integration via MCP
20:32
The Messaging Connector Protocol (MCP) is positioned as a critical feature for the next generation of developer tools. The adoption of MCP is accelerating, with the platform building out 80+ named tools to maximize utility and coverage for agents.
-
Scaling and Observability Challenges
17:32
Scaling support and infrastructure requires moving beyond simple staffing increases. The discussion emphasizes the need for deep observability into the entire email lifecycle—from sending to final delivery status (e.g., knowing if an email landed in the Promotions tab)—to provide true value to users.
More digests on Email Infrastructure
Technical details
-
Email Deliverability & Throttling
720s
High-volume email sending requires respecting mailbox provider rules (e.g., Gmail). Sending 100,000 emails must be managed in batches and spaced out across different IP blocks to avoid throttling. The system must analyze engagement metrics (opens, deletes, archives) to dictate the sending queue.
-
Architecture and Development Stack
1200s
The platform utilizes a headless backend architecture, separating the API from the frontend components (like React Email). The architecture is designed for maximum reusability, allowing developers to build the UI using components while the core logic remains in a private API.
-
Cloud Infrastructure Complexity (AWS)
1400s
Building a robust service on AWS requires integrating multiple services (SNS for events, CloudWatch for logs, SQS for queues, etc.). This creates a significant operational footprint that must be managed to handle the high volume of event data generated by a communication platform.
-
AI/Agent Interaction
The platform is designed to support agentic workflows, allowing agents to perform complex actions like reading pricing in Markdown, setting up accounts, and sending emails programmatically. The focus is on making the API the primary interface for these automated tasks.
Mentioned resources
- React Email
- Resend
- AWS
- Messaging Connector Protocol (MCP)
Channel & topics
Watch on YouTube · Back to latest
This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.