← Agent use casesEmail for AI agents: inboxes your agent can read, wait on and reply from
Give Claude Code, Cursor, Codex or your own agent its own email address. Create inboxes over MCP, HTTP, SDK or CLI, wait for new mail, get one-time codes and links extracted, read threads and attachments, and send or draft replies for a human to approve.
The SDK examples use an authenticated Kivel client. Set up the SDK or connect your agent over MCP.
What an agent email inbox is
An agent email inbox is an address that software, not a person, reads. Kivel creates the address on socketspace.xyz and gives your agent tools to wait for the next message, read it as structured data and act on it. The agent never needs access to your personal mailbox.
Typical uses are signing up to a service and confirming the email, receiving password reset and magic link emails during tests, reading invoices or reports that arrive by email, and answering simple messages with a human approving each reply.
The tools your agent gets
Over MCP the agent calls create_email_inbox for a new address, wait_for_email to block until mail arrives, list_emails and list_email_threads to read history, get_email_thread for a whole conversation and get_email_attachment to download a file. Every message comes back with its one-time codes and links already extracted, verification links first, so the agent does not parse HTML.
send_email sends from the inbox’s own address. email_draft creates a draft and can submit it for human approval with an optional scheduled send time; inboxes with approval required reject direct sends. email_inbox_rules sets allow and block lists for senders. The same operations are available over the HTTP API, the @kivel.io/sdk TypeScript SDK and the kivel CLI.
const inbox = await kivel.createEmailInbox({ activeDays: 3 });
// Use inbox.address in the signup form, then:
const result = await kivel.waitForEmail(inbox.id, { timeoutSeconds: 20 });
const message = result.messages?.[0];
console.log(message?.codes[0], message?.links[0]?.url);Keep a human in the loop for outgoing mail
Turn on approval for an inbox and the agent can only send through drafts. Each draft goes to you for review, and the agent waits for your decision before anything is delivered. Reviews expire after at most 24 hours.
Sending also requires a verified owner email on the Free plan and is capped per day and per month, so a looping agent cannot send unlimited mail.
Plans and limits
Free includes one inbox that stays active for one to seven days and 30 outgoing deliveries a month. Pro includes 10 inboxes and 500 deliveries a month, and Team includes 50 inboxes and 3,000 deliveries a month. Paid inboxes stay active while the plan is active. Each inbox keeps its latest 100 messages.
Addresses use the socketspace.xyz domain. Custom domains, IMAP and SMTP access are not available yet.
How does Kivel compare with AgentMail?
Both give agents inboxes over an API. AgentMail focuses on email alone and supports custom domains. Kivel puts email next to webhook inboxes, mock APIs, monitors, memory and human approvals behind one MCP server, extracts codes and links for you and requires approval for outgoing mail when you ask it to.
How do I connect my agent?
Add the Kivel MCP server to Claude Code, Cursor, Codex or another MCP client, approve the login in your browser, then ask the agent to create an email inbox. The setup page has the exact command for each client.