Developer betaAn email identity for every agent

Give every AI agent its own inbox.

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

Get started Read the quickstart

Free during the beta. Send from your first agent right after signup.

Research agent research@agents.cyberpigeon.ai

Ready to send

Alex · Research requestCould you put together a brief on our competitors? 9:12

Re: Research requestHere’s the brief, with sources and next steps. Delivered

Agent keysm_•••••••••••• Read + send

Example only. Your agents, addresses and messages appear in your console.

REST API and OpenAPI specification
MCP server for Claude, Codex and ChatGPT
Keys scoped to each agent
Hosted on Microsoft Azure

How it works

An inbox is one API call away.

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

Create a mailbox
Give each agent an address and its own scoped key.
Send and receive
Keep messages, replies and delivery events together.
Let the workflow continue
Poll for new messages and decide what happens next.

Read the API reference

Shell

curl "$CYBERPIGEON_URL/v1/mailboxes" \
  -H "Authorization: Bearer $CYBERPIGEON_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.

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.

Reach people where they work

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

Pick up where the reply arrives

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

Give each role its own identity

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

Why agents need email

Conversations

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

Connect your AI app

Give Claude, Codex or ChatGPT an inbox.

Add the hosted MCP server, sign in, and choose the agent and permissions the app may use. Nothing to install, and you can revoke access at any time.

Connect your AI app

Add the MCP server
Paste https://cyberpigeon.ai/mcp into your app’s connector settings.
Sign in and choose access
Pick one agent with read, send or both, or a new inbox for the app.
Let it work
The app can read, wait for, send and reply to email with the same limits as the API.

Built for agents

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, on agents.cyberpigeon.ai or, on paid plans, your own domain.

Just the access it needs

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

Know what happened

Follow each message from queued to sent to delivered. Retry with the same idempotency key to avoid duplicate sends.

Trust

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.

Keys you can scope and revoke

Give each integration its own key, limited to one agent and to reading, sending or both. Secrets are shown once and stored as hashes.

Persistence on Azure

Mailboxes and messages live in a private PostgreSQL database on Microsoft Azure.

From idea to implementation

For practical notes on reliable workflows, permissions and delivery, read the Cyberpigeon blog.

Your next agent deserves an inbox.

Start with one agent and see what it can do.