让AI代理选中你的产品：Resend的AEO实践
做法与步骤
- 先发优势来自React Email模板：开发者在选邮件服务商前就用它构建模板，即使通过SendGrid发送，Resend代码已进入仓库，为后续切换埋下伏笔。
- 定价页加.md后缀返回机器可读表格，让代理一次请求获取价格，类似Supabase做法；作者建议检查自家定价表能否直接回答客户问题。
- Resend的MCP服务器工具数从约20个增至80多个，目标是让聊天客户端能完成仪表盘所有操作；但作者也观察到工具调用结果可能过大，减少工具数不一定缩小响应。
- 作者建议设计MCP服务器时展开日常调用的结果，看模型实际需要多少数据，并参考Anthropic关于返回更少数据的建议。
- 代理选中SDK只是开始，投递、点击追踪等业务仍需处理；共享追踪域名可能因一个客户滥用而连累其他客户，Resend因此推出自定义追踪域名。
- Resend保留免费层以获取信任，但需应对垃圾邮件注册；作者提到其300万美元安全承诺和反滥用手册。
对实践的启示
做AI应用或工具的人应把产品信息（定价、文档）做成机器可读格式，在开发者工作流中提前植入代码，并设计精简、结果可控的MCP工具；同时注意代理推荐后的实际业务环节（如投递、反滥用）才是长期信任的基础。
作者承认的反方与局限
作者提到减少MCP工具数量本身并不能解决工具调用结果过大的问题；此外，免费层可能被垃圾邮件发送者利用，需要额外投入反滥用。
原文摘引
Add .md to the URL and the agent gets a table it can read in one request.
Reducing the tool count wouldn’t by itself make that response any smaller.
If one customer uses that domain for phishing and it gets blocklisted, links in another customer’s perfectly legitimate emails can suffer too.
▸ 展开原文全文（40 段，抓取自 Latent Space）
Today’s podcast comes from a real life mystery: We are big fans of Cloudflare’s developer platform, and Cloudflare Email is a convenient tool especially when all your domains are already on Cloudflare.
So why do agents keep suggesting we use Resend despite having an existing “home bias” and much larger incumbent player?
Well, we got the guy who “does AEO for resend” - the CEO of AEO, Zeno Rocha, who has been writing about AEO since 2024 and Agent Experience since Feb 2025, on the pod today:
In a recent AEO study, Claude Code picked Resend first in 64 of the 102 email recommendations the researchers could extract. SendGrid came first seven times, yet showed up 55 times as an alternative. If the developer asks an agent to implement email and accepts the patch, how often does anyone get around to trying the second choice? The study breaks down the results by model and app. Our more recent comprehensive AEO study was a bit more competitive, with Postmark coming up top for most models.
Zeno Rocha, Resend’s co-founder and CEO, joined us to walk through what happens on both sides of that pull request. He says Resend had 4.3 million users and 120,000 paying customers when we recorded. He discovered one of them, Warner Bros. Discovery, by sorting through short .com domains in the customer database on a Saturday.
The developer gets there before the model
Resend’s first useful bit of distribution was an email template. While Zeno and his team were building the sending API, developers kept telling them how painful it was to get the email itself to look right. So they released React Email. You could build a template with it and send it through SendGrid. They even documented how. By the time a developer needed a different provider, some of Resend’s code was already in the repo. React Email
Now try the same journey as an agent comparing providers. Resend’s pricing page has a slider. A person can drag it to the right volume and read off the price. Add .md to the URL and the agent gets a table it can read in one request. That’s the kind of change I liked in our Supabase interview too. You can ask whether a model has heard of your product. You can also open your own pricing table and see whether it can answer a customer’s question.
80 tools, or two?
When we recorded, Resend’s MCP server had grown from roughly 20 tools or fewer at launch to more than 80. Zeno wants someone working in a chat client to be able to do what they can do in the dashboard. Sending an email gets the demo working. Inviting a teammate, checking usage and managing billing account for some of the long tail. The design looks especially interesting alongside Cloudflare’s Code Mode server, which exposes its API through two tools, search() and execute().
Zeno describes opening the collapsed tool calls in his own sessions to see what the agent actually did. In one, the result was too large to fit in context. Reducing the tool count wouldn’t by itself make that response any smaller. For someone designing an MCP server, that’s a cheap experiment worth borrowing: expand the result of a call you make every day and see how much of it the model actually needs.
What happens after “send”?
Getting an agent to pick the SDK still leaves the entire business of delivering the mail. Take click tracking. A provider can rewrite links through a shared tracking domain so it can count clicks. If one customer uses that domain for phishing and it gets blocklisted, links in another customer’s perfectly legitimate emails can suffer too. Zeno explains why Resend introduced custom tracking domains and why he wants to keep the free tier even though spammers can sign up for it. Custom tracking domains · Resend’s $3M safety commitment
Watch the domain setup and pricing walkthroughs if you build developer tools. Stay for the last stretch if you know Zeno from Dracula. We get into what it’s like to build a company with a family and how much of a founder’s job comes down to finding a name that other people actually use.
Show notes
- Zeno’s original Dracula announcement — the editor theme he launched in 2013.
- Zeno on what Claude Code chooses — his reading of the recommendation study and the differences between model versions.
- Resend’s MCP server — the integration behind the tool-count discussion.
- Anthropic on writing tools for agents — concrete approaches to returning less data when a tool result fills the context window.
- Resend’s anti-abuse handbook — what happens when a new sender signs up and where the team intervenes.
Chapters
0:00 Cold open
0:59 From Dracula to email
5:02 When agents pick the API
6:54 Getting into the inbox
13:28 What tracking measures
17:05 Paying for trust
19:44 The DNS hurdle
23:55 React Email’s wedge
27:01 Measuring adoption
31:58 Owning the mail stack
37:55 Designing the MCP
46:29 CLI, SDKs and craft
52:41 Mail for agents
58:28 Writing for machines
1:06:00 Winning recommendations
1:12:14 Enterprise and pricing
1:16:51 Building with a family
1:23:26 Naming a category
| | Resend - Zeno Rocha - Transcript.txt94.65 KB • PLAIN File |