scargo mail
ConsoleStart building
Private betaAn email identity for every agent

Give your AI agents
an inbox.

The email API for AI agents. Provision an address, issue a scoped key, and build workflows that send, receive, and follow the conversation.

Explore the API Open console

Private beta · Mail activation is in progress.

⌘   Built around your API↔   Send, receive, and reply⌑   Keys scoped to each agent☁   Hosted on Azure

Beyond the chat window

Real work needs
a return address.

AI agents need email when a task depends on people, services, or replies that arrive later. An inbox gives the conversation somewhere to continue.

Why agents need email
01

Reach people where they work.

Request a quote, collect a document, or ask a customer a question. They can answer from the inbox they already use.

02

Pick up where the reply arrives.

Keep the address and correspondence across agent runs. Your application resumes the task when new information arrives.

03

Give each role its own identity.

Assign a mailbox to a role or project, with credentials scoped to the correspondence that agent needs.

From idea to implementation

Build the complete conversation.

Use cases · 01

Workflows that need an inbox

Supplier coordination, support, document collection, and authorized account invitations.

Explore the workflows ↗ Developer guide · 02

Your first agent mailbox

Real REST examples for provisioning, authentication, sending, event polling, and replies.

Read the quickstart ↗ Buyer’s guide · 03

Choose your email API

Compare Scargo Mail, AgentMail, and Resend by integration model and current availability.

Compare the approaches ↗

An inbox is just
an API call away.

Build email into your agent’s workflow with familiar HTTP requests. Your framework, your model, your logic.

1
Create a mailbox

Give each agent an address and its own scoped key.

2
Send and receive

Keep messages, replies, and delivery events together.

3
Let the workflow continue

Poll for new messages and decide what happens next.

Read the API reference
cURL 
curl "$SCARGO_URL/v1/mailboxes" \
  -H "Authorization: Bearer $SCARGO_ACCOUNT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Research agent",
    "local_part": "research"
  }'

201 Created A mailbox and its scoped API key

Example request and response. Use your account key to create a mailbox; use the returned agent key for mail. Copy includes this API’s base URL.

Everything an agent needs
to work over email.

A persistent identity and a conversation your agent can pick up whenever it’s ready.

An address of its own.

Create a separate mailbox for each agent. Give research, support, and operations their own place in the conversation.

agent@agents.scargo.ai

Just the access it needs.

Issue a key for one mailbox, with read, send, or both permissions. Rotate or revoke access from your console.

One agent. One scoped key.

Know what happened.

Follow queued messages through delivery events. Retry requests with the same idempotency key to avoid duplicate sends.

Queued → sent → delivered

Vendor researchExample conversation
AL
Alex

Find three vendors that can support our EU expansion.

S
Research agent

I’ve shortlisted three options. Are there any budget constraints?

Reply in the same thread
AL
Alex

Keep the first year under €20,000.

S
Research agent

Got it. I’ll narrow the shortlist and update the brief.

The conversation
doesn’t end at send.

Read the response, keep the thread, and carry on. Email becomes part of the workflow your agent already understands.

  • Reply with the original conversation’s threading headers
  • Read plain text, HTML, and attachment metadata
  • Pick up new messages through a durable event cursor
Explore messages and replies

Built for delegated work.

You keep control of the accounts, credentials, and permissions behind your agents.

Separate by default

Account boundaries and mailbox permissions apply to every authenticated request.

Persistence on Azure

Mailboxes and messages live in a private PostgreSQL database. API keys are stored as hashes.

Your next agent
deserves an inbox.

Explore the API today. Build toward your first email workflow.

Start buildingExplore pricing