Bento

Connect an agent via an official MCP server G

Agent access

Drive the product through a documented public API G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Point an agent at llms.txt or agent-oriented docs G

Agent access

Operate the product with natural-language commands G

Agentic features

Set up automations that run autonomously in the background G

Agentic features

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Build against official SDKs G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Rely on versioned APIs with a documented deprecation policy G

Api quality

Subscribe to events via webhooks G

Agent access

Issue scoped/least-privilege API credentials for an agent G

Agent access

Use an official CLI G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Send one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends C

Transactional api

Build audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes C

Segment core

Define rules that trigger actions automatically on events G

Fire a custom event from my product and have it trigger an automation for exactly that person C

Event triggers

Build multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules C

Automation core

Create and update segments, tags, or lists programmatically and read back exactly who is in them C

Api segments

Compose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop C

Campaign core

Create, update, and suppress contacts with custom properties through the API at production scale C

Api contacts

An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send C

Agent campaigns

Read opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time C

Reporting core

Export all of my data in open formats and leave G

Export my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve C

Export

Authenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification C

Domain auth

Create and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard C

Api campaigns

Read per-person engagement history — what was sent, opened, clicked — through the API for any contact C

Api access

Subscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload C

Webhooks

Prevent my data from being used to train AI models G

Self-host the core product G

Unsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default C

Suppression

An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working C

Agent access

Attribute signups or revenue to specific emails and flows, not just opens and clicks C

Attribution

Perform bulk operations across many items at once G

Do everything through the API that I can do in the UI G

Migrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state C

Import migration

Transactional email is kept separate from marketing — its own templates, suppression rules, and reputation — so a receipt still delivers to an unsubscribed contact C

Transactional hygiene

Schedule recurring jobs or workflows G

An agent can translate a plain-language audience description into a real segment via the platform's programmatic surface C

Agent segments

Choose where my data is stored (region/residency) G

Connect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrations C

First party integrations

Have the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer C

Ai content

Mint scoped or read-only API credentials so an agent or contractor can read analytics without the power to send C

Scoped access

Pull campaign and flow performance metrics through the API into my own warehouse or dashboards C

Api metrics

See bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades C

Deliverability signals

See where any individual person sits inside an automation and pull or re-enter them without breaking the flow C

Flow operations

A/B test subject lines or content variants and have the winner picked from real engagement C

Experiments

Control data retention and deletion G

Design on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients C

Editor

Manage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control C

Templates as code

Opt out of telemetry and usage tracking G

Read the product's source under an open license G

Version, review, and roll back my automations G