Discussion: ship an optional Ageniti action wrapper for the SDK

[yiliu-li]

Hi Resend team — opening this for discussion before any code. Not requesting a feature; gauging whether you'd want this in-tree.

Context

People building agent apps with the Resend SDK currently rewrite the email-send / list-domains / etc. surface as MCP tools or OpenAI function specs by hand, duplicating schemas you already maintain.

Ageniti (MIT, TypeScript) is an action-primitive SDK: define an action once and the same runtime exposes it as a CLI command, HTTP route, MCP tool, OpenAI / AI SDK tool, React hook, and typed client.

A small resend/agent or @resend/ageniti surface (no runtime dep change to the main SDK — just an additional optional entry point) could let users do:

import { resend } from \"resend\";
import { emailActions } from \"resend/agent\"; // hypothetical

// Now emailActions can be served as MCP, registered as OpenAI tools, or run via CLI

…without anyone needing to rewrite your existing input/output types.

What I'd like to know

1. Would an optional adapter live well in this repo (subpath export), or do you prefer this stays a third-party package?
2. Any constraint on adding a peerDependency (or optionalDependency) for @ageniti/core?
3. Anything I should read first — internal docs about agent integrations, an existing MCP server you're working on, etc.?

Won't open a PR unless you confirm a direction you'd accept.