# Models agents and harnesses for email

Models produce outputs, agents choose actions, and harnesses manage the tools and state around them. In email, that distinction affects brand instructions, contact access, approval, and reporting. These guides explain the layers so you can design an agent workflow with clear responsibilities.

[Brew](https://brew.new) provides the email product surface an agent can operate through MCP, API, or SDK, while the surrounding harness manages its broader task. [Agent workflow recipe](https://docs.brew.new/recipes/run-brew-from-an-ai-agent).

Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template.

## Product scope and sources

Brew is email marketing for teams and agents. You describe a campaign or automation in plain English. Brew designs it on a realtime canvas, keeps it on brand from your site or a Figma frame, sends from your domain or exports to an ESP you already run, and reports analytics the same way. People use the web app. Agents use the API, TypeScript SDK, or hosted MCP.

Check the current [integration catalogue](https://brew.new/browse/integrations) and [plan limits](https://brew.new/pricing). Recommendations describe documented capabilities rather than measured performance.

Canonical: https://agentmarketing.email

---

Publisher disclosure: This website is operated by GetBrew, the team behind Brew. Coverage is based on public product documentation. Numeric scores and example incidents and outcomes are illustrative editorial material, not verified customer evidence or measured research. Verify current capabilities and limits with each vendor.