AgentRelay

PilotSandbox inboxes for your agents

Give your agent an inbox. Keep control of every action.

Give agents a dedicated email address. Review their conversations, set sending limits, and approve the messages that need your attention.

Create a sandbox inboxExplore the current pilot
Illustration with example data: a reply to a vendor, waiting for finance to approve it.
  • REST API
  • MCP beta
  • Sending rules
  • Human approval
  • Malware-scanned attachments
  • Signed receipts

How it works

One address in, reviewed mail out.

Each agent gets its own inbox. Every outgoing message passes your rules first — and anything that needs a person waits for one.

  1. Step 01

    An inbox for each agent

    Keep conversations and drafts together, with a dedicated address for each workflow.

  2. Step 02

    Rules before sending

    Choose who agents can contact and which messages need your approval.

  3. Step 03

    Review incoming mail

    See safety warnings next to each message. Attachments are scanned for malware, and only a rebuilt copy of a clean file can be downloaded.

  4. Step 04

    A record of every message

    See what went out, what is waiting for approval, and what needs you.

Communicate

A real inbox, not a send-only pipe.

  • A dedicated address for each agent
  • Threads, replies and forwards
  • Drafts you can read before they go out
  • REST API and MCP beta

Control

Every outgoing message meets your rules first.

  • Choose who agents can email
  • Sending limits and quiet hours
  • Drafts-only and replies-only modes
  • Approval before contacting someone new

Prove

Every decision leaves a record.

  • A record of every outgoing message
  • Why each message is waiting for approval
  • Receipts you can verify by link (Scale)
  • Message counts for your workspace

An inbox tells you where a message came from. AgentRelay also shows which rule allowed it, whether a person approved it, and what was sent.

For developers

One request. Your rules decide.

Use the REST API or MCP beta to read mail, save drafts, and send. Every outgoing message is checked against your rules first.

  • API keys you can limit to one agent or inbox
  • Safe retries: a repeated request won’t send twice
  • Messages that need a person wait in Approvals
Read the developer guide
send-message.http
POST /api/v1/send-intents
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: 61a6cbe7-...
Content-Type: application/json

{
  "inbox_id": "inb_01J...",
  "kind": "reply",
  "purpose": "vendor_quote_request",
  "to": [{ "email": "quotes@supplier.example" }],
  "subject": "Quote request: 250 units"
}

// → checked against your rules: sent, waiting for approval, or blocked

Sending controls

Decide what your agents can send.

Start with draft-only access, set recipient limits, and review messages before they leave your workspace.

See how it worksCompare plans

Track mail usage

See how many messages come in and go out. Usage counts are not a bill.

Keep permissions in your hands

Instructions inside an incoming email cannot change your agent’s sending permissions.

Spot delivery issues

If we can’t confirm a message went out, we flag it so it isn’t sent twice by mistake.

Know why a message is waiting

Read the draft and the reason it needs approval, then approve & send or reject it.

Start with a sandbox inbox today.

Create an inbox, point an agent at it, and approve the first messages yourself.

Create a sandbox inboxCompare plans