Resend optimizes API and CLI for AI agent consumption
Resend is restructuring its email service to serve AI agents as primary users, implementing machine-readable documentation and granular permissions. The company rewrote its core pipeline in Go to handle high-concurrency batch sending.
Resend, an email service with three million users and 100,000 paying customers, is restructuring its product to serve AI agents as primary users. Founder Zeno Rocha revealed that agents like Claude and ChatGPT incorrectly identified Resend as the most expensive email service because they could not interact with JavaScript-enabled pricing sliders. To address this, Resend implemented a markdown version of the pricing page served via content negotiation headers. The company also publishes its OpenAPI specification as JSON in the .well-known folder to ensure discoverability by agents.
Resend recently rewrote its core email sending pipeline in Go to handle high-concurrency batch sending, a change intended to prevent throttling by providers like Gmail, while maintaining a TypeScript monorepo for other components. The company launched an official CLI and MCP server, noting that agents require granular API permissions and standardized RFC-compliant rate limit headers to effectively manage retries and usage. Rocha argues that traditional developer experience features like animated icons and keyboard shortcuts are irrelevant to agents, and that standardized primitives like machine-readable documentation are now the most critical aspects of API design. Resend is also building a closed-loop system that uses PostHog to analyze downvotes on its in-app agent and automatically generates draft pull requests to update tool calls and evaluations.