AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Designing for Agents — Zeno Rocha, Resend

Collected Nov 10, 2026

Resend co-founder and CEO Zeno Rocha appeared on the Latent Space podcast to explain how a smaller email provider ends up as the default suggestion when developers ask coding agents to add email. The episode frames the question around a concrete observation: the hosts use Cloudflare's developer platform and Cloudflare Email, yet agents still recommend Resend. Rocha, who has written about answer engine optimization since 2024 and about agent experience since February 2025, walked through both sides of that recommendation.

The numbers came from a recent AEO study. Out of 102 email recommendations the researchers could extract, Claude Code picked Resend first 64 times. SendGrid came first seven times but appeared as an alternative 55 times. A later, more comprehensive study was more competitive, with Postmark coming out on top for most models. The hosts raise the practical consequence: if a developer accepts the agent's first patch, the second-choice provider may never be tried at all. Resend's stated scale at recording time was 4.3 million users and 120,000 paying customers.

Much of that reach predates agents. React Email, Resend's component-based email template library, was built because developers kept saying the sending API was not the hard part. Getting the email itself to look right was. React Email could be used to build a template and then send it through SendGrid, and the team documented that path. The effect, as described on the podcast, is that some Resend code was already in a repository by the time a developer considered switching providers.

The podcast draws a parallel between that developer-first wedge and how agents now compare providers. Resend's pricing page uses a slider that a person can drag to a volume and read off a price. Appending .md to the URL returns a table that an agent can read in a single request. This suggests a cheap audit any product team can run: ask a model what it knows about your product, and check whether its tooling can answer a routine pricing question from your public pages. Tables and machine-readable variants of the same content are easier to consume than interactive widgets, because an agent has no pointer to drag.

On the protocol side, Resend's MCP server grew from roughly 20 tools or fewer at launch to more than 80 by recording time. An MCP server exposes a set of actions a model can call, and each tool is described to the model in its context. Rocha said the goal is parity with the dashboard from inside a chat client: sending an email makes the demo work, while inviting a teammate, checking usage and managing billing cover the long tail. He contrasts this with Cloudflare's Code Mode server, which exposes an API through just two tools, search() and execute(). That design keeps the tool list small but pushes more of the work into generated code.

The interview adds a caveat that matters more than tool count. Rocha described expanding collapsed tool calls in his own sessions to see what the agent actually did, and in one case the result was too large to fit in context. Fewer tools would not shrink that response. The practical advice is to inspect the payload of a call you make every day and see how much of it the model really needed. Trimming verbose fields can free context for the actual task; a large tool catalog and a large tool result are separate problems.

Getting an agent to pick the SDK is only half the job; the mail still has to arrive. Click tracking is one place where provider design has downstream consequences. Providers often rewrite links through a shared tracking domain to count clicks. If a spammer uses that shared domain for phishing and it lands on a blocklist, links in other customers' legitimate mail can be affected too. Resend introduced custom tracking domains so customers can send tracked links under their own domain. Rocha also said he wants to keep the free tier even though spammers can sign up for it, and the podcast references a $3M safety commitment and an anti-abuse handbook describing where the team intervenes when a new sender signs up.

The send path itself has a known hurdle that agents do not remove: DNS. Sending mail on a custom domain means setting up records that prove ownership and authorize the sender, which is a typical point of friction for a developer or an autonomous agent working through a setup checklist. In practice, a smooth SDK install does not guarantee deliverability; domain authentication and reputation management remain operational work.

The conversation closes on company building. Rocha previously launched the Dracula editor theme in 2013, and the episode touches on running a company with a family and on how much of a founder's job is finding a name other people actually use.

Why it matters: Product teams now compete for a first recommendation that an agent may make once and a developer may never revisit, which makes machine-readable docs, pricing and examples part of distribution rather than polish. MCP server authors face a concrete trade-off between broad dashboard parity and bloated tool lists and oversized results, and inspecting real call payloads is the cheapest way to find the difference. Email providers in particular are judged on deliverability and abuse handling, not just SDK ergonomics, so the recommendation win only pays off if the mail behind it lands.

Read at Latent Space

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

Where does answer engine optimization (AEO) end and agent experience begin? Inside Resend, from the docs that help Claude Code pick an email API to the tools it uses to send.