Lifecycle email your agent runs.

How it works

1. 1

   Your app sends events

   One REST call per event, with an Idempotency-Key, so a retry never counts twice. Each event creates or updates the person it is about.

2. 2

   You ask your agent for the flow

   Describe the emails in plain words. Your agent writes the flow. Ringmaster refuses a misspelt merge field or an unverified domain before it saves, and you confirm before it mails anyone.

3. 3

   Ringmaster sends it

   Each step waits for the recipient's daytime, skips people who already did the thing, and stops as soon as their consent does.

Rules your agent can't break

They live in the server, so they hold whatever a prompt says.

Nobody gets an email twice

Every send claims its row before the email goes out, under a key that stays the same across retries. A crash or a retry never mails twice.

An unsubscribe is final

One check decides whether an address may get mail in a topic. Every email carries a one-click unsubscribe link and header, and a bounce or complaint stops every topic.

Nothing lands at 3am

Delays move into 08:00 to 20:00 in the recipient's time zone, taken from their profile or their country.

A person says go

Activating a flow, sending a campaign and suppressing an address wait for a yes in your agent's client. Scheduling a campaign is a dry run until you execute it.

Bad sending stops itself

When bounces or complaints climb, a circuit breaker pauses your sending until we have looked. A monthly cap sits under every account.

Deleting a person deletes them

One API call erases a profile and every row that mentions them, sends and events included.

Your agent gets 69 tools

Everything you can do in Ringmaster's dashboard is an API route, and every route is an MCP tool. Nine skills teach your agent when to use each one. Tools marked ask a person first.