Email and Artifacts in a pilot, with access on request

Email for AI agents

Every agent gets its own inbox, created and used through the API or MCP.

Request pilot access Start with one command

What an agent does with an inbox

Creates its own inbox, on the DockBay domain or on yours, with ownership verified through DNS.
Sends and replies in the same conversation, in text or HTML, with attachments; replies to all and forwards.
Waits for the answer from a cursor, without losing what arrived before.
Notifies other systems by signed webhook or WebSocket.
Searches conversations, subjects, senders and attachments.
Never sends the same message twice by mistake: every send has an explicit state.

Start with one command

With the key you receive in the pilot.

Claude Code (MCP)

claude mcp add --transport http dockbay https://api.dockbay.io/mcp \
  --header "Authorization: Bearer $DOCKBAY_API_KEY"

Then, in plain language: “email ana@example.com and wait for the reply”.

REST

# create the inbox
curl -X POST https://api.dockbay.io/v1/inboxes \
  -H "Authorization: Bearer $DOCKBAY_API_KEY" -H "Content-Type: application/json" \
  -d '{"local_part": "agent"}'

# send a message
curl -X POST https://api.dockbay.io/v1/inboxes/agent@inbox.dockbay.io/messages \
  -H "Authorization: Bearer $DOCKBAY_API_KEY" -H "Content-Type: application/json" \
  -d '{"to": "ana@example.com", "subject": "Order received", "text": "Hi Ana, I got your order and will get back to you today."}'

Pilot limits

50 recipients per message.
Messages up to 25 MB, attachments up to 10 MB.
Messages kept for 30 days.
Waits of up to 25 s per MCP call; the CLI waits longer.