
Designing for Agents — Zeno Rocha, Resend
About this episode
From the show’s notesA coding agent opens a pull request and picks an email provider for you. How did it choose? Resend co-founder and CEO Zeno Rocha explores answer engine optimization (AEO) through a concrete example: which email provider does Claude Code recommend, and how does that change across model versions? Then comes the agent experience itself. Once the agent picks Resend, can it find the price, set up the account and send its first email?
We also follow an email after the API call succeeds. Zeno explains what happens when Gmail throttles a burst, why a tracking pixel can give you the wrong idea about who opened a message, and how one abusive sender can put other customers’ mail at risk. Then we get into the product decisions: giving an agent 80+ named MCP tools, letting it read pricing in Markdown, and letting it register for a service on its own.
Read the show’s notes in full
Explore the references
• Zeno’s analysis of what Claude Code recommends: x.com/zenorocha/status/20277578…
• Resend’s $3M email safety pledge:
resend.com/blog/3-million-to-ma…
• React Email, the open-source email components:
react.email
• The proposed agent registration standard shown on screen:
workos.com/auth-md
Chapters





