Docs

The documentation ships with the product.

RelayFlow is pre-release and distributed privately, and its documentation goes out with it rather than being published here. Rather than show you a page of placeholders, here is honestly what it covers.

REST API reference

The normative contract for the whole platform: sending, batch and scheduled send, the receiving inbox, domains, mailboxes, suppressions, agent configs and runs, API keys, webhooks, and request logs. Every example in it is plain curl.

Agent budgets

How the per-mailbox and organisation-wide daily spend caps are calculated, when they reset, and what happens to a run that would exceed one.

Inbound SES setup

Wiring a receipt rule to S3 and a queue, and pointing a verified domain at your deployment so mail actually arrives.

Outbound SES setup

Running the send path on SESv2 instead of SMTP, including how errors are classified retryable against terminal.

The REST API is the normative contract — the SDK and the MCP server are conveniences over it, not a separate surface. If you can make an HTTP request, you can use everything.