Email infrastructure company Resend is building its documentation and tooling with AI coding agents in mind. In a Latent Space podcast episode, Resend's Zeno Rocha discusses where answer engine optimization (AEO), the practice of making content easy for AI systems to find and cite, ends and agent experience begins. The show notes say the conversation covers the documentation that helps Claude Code, Anthropic's coding agent, choose an email API, and the tools the agent uses to send email. Those are different design problems. Helping an assistant recommend a service depends on accurate, discoverable documentation. Helping an agent send messages depends on how actions are exposed and controlled. The episode is a discussion rather than an announcement, and the show notes do not disclose new features, pricing or usage figures. For Australian businesses and professionals, nothing changes directly, because no product change or pricing is announced. Teams that let AI agents send email on their behalf should treat it as a compliance question. Commercial electronic messages sent to or from Australia are covered by the Spam Act 2003, which requires consent, sender identification and an unsubscribe option. Any personal information in templates or agent prompts falls under the Privacy Act 1988. Keeping a human approval step for outbound email until those controls are tested is a sensible starting point. Checking how a coding assistant currently describes your own product in its API docs is a low-cost test.