Replicate handles model inference. MultiMail handles the email boundary — approval gates, delivery, and an audit trail for whatever your models produce.
Replicate gives agents access to hundreds of open and proprietary models through a single API. When those models generate text, images, or structured output that needs to reach a human inbox, you need a separate layer to handle delivery safely. Model output and email sending are different responsibilities with different failure modes.
MultiMail sits between Replicate's predictions and your recipients. It provides oversight modes that let you require human approval before any model-generated content leaves your system, log every send decision for compliance review, and route inbound replies back to the agent that sent the original message.
The integration is direct: call Replicate to run inference, pass the output to MultiMail's REST API or MCP server, and let MultiMail handle delivery policy. No shared SDK required — both services expose clean HTTP APIs that compose naturally in any language or agent framework.
Replicate predictions can produce content you wouldn't want sent without review. MultiMail's gated_send and gated_all modes hold outbound messages for human approval before delivery, regardless of how confident the model was.
Every send through MultiMail records the message, sender identity, recipient, and timestamp in the audit log (GET /v1/audit-log). When model-generated emails are involved, this log is the evidence trail regulators and auditors ask for under CAN-SPAM and GDPR.
When recipients reply to a Replicate-generated email, MultiMail webhooks notify your agent, which reads the message via GET /v1/mailboxes/{mailbox_id}/emails/{email_id}. The agent can continue the thread without polling or managing raw SMTP.
MultiMail mailboxes are owned by your account and cryptographically tied to your domain. The model that generated the content doesn't appear in email headers — your verified identity does.
High-stakes workflows (customer outreach, medical summaries) can require gated_all approval. Internal digest pipelines can run in monitored mode. The mode is set per mailbox, not per request.
No code, no dashboard. Paste this to your AI agent — it connects MultiMail, creates an inbox, and builds the flow for you.
Sign up at multimail.dev, create a mailbox (custom domain or @multimail.dev subdomain), and copy your API key from the dashboard. Set the mailbox oversight mode to gated_send for initial testing — this lets you inspect outbound messages before they deliver.
Install the Replicate JavaScript or Python client and export your Replicate API token. You'll authenticate to both services independently — MultiMail via Bearer token, Replicate via its own token header.
Make a Replicate prediction call, wait for the result, then post it to MultiMail's POST /v1/mailboxes/{mailbox_id}/send endpoint. Start with a text generation model so you can inspect the full round trip before adding multimodal steps.
Because the mailbox is in gated_send mode, the message is queued. Use GET /v1/oversight/pending to see it, then POST /v1/oversight/decide to approve. Check your inbox to confirm delivery.
Configure a webhook endpoint in the MultiMail dashboard pointing to your agent server. When a recipient replies, MultiMail POSTs the event to your endpoint. Read the message via GET /v1/mailboxes/{mailbox_id}/emails/{email_id} and feed the body back to Replicate for a follow-up prediction.
Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a hosted MCP server. Formally verified in Lean 4.