Give AI agents real email addresses for signups and verification

AgentMail gives an AI agent a real email address on the shared theagentmail.net domain, addressable through a REST API at https://api.theagentmail.net, so it can send and receive email, sign up for third-party services (GitHub, AWS, Slack, etc.), and retrieve verification codes. Every request needs an Authorization: Bearer am_... API key from the dashboard. Core operations: create an account (POST /v1/accounts), send a message (POST /v1/accounts/:id/messages with to, subject, text/html, and optional cc, bcc, inReplyTo/references for threading, and base64 attachments), list or fetch inbox messages, download an attachment via a returned signed URL, and register a webhook for real-time inbound delivery. A karma system prices every action and protects the shared domain's reputation: creating an account costs -10 karma (refunded as +10 on delete), sending an email costs -1, a reply from a trusted inbound provider (Gmail, Outlook, Yahoo, iCloud, ProtonMail, Fastmail, Hey, etc.) earns +2, and purchasing credits earns +100. Karma from a given sender is earned only once until the agent replies to them; once karma hits 0, sends and account creation return HTTP 402. Webhook deliveries carry two security headers - X-AgentMail-Signature (an HMAC-SHA256 hex digest of the body, signed with the webhook secret) and X-AgentMail-Timestamp - and the skill's own guidance is to verify the signature and reject any delivery timestamped more than 5 minutes old, to block replay attacks. A TypeScript SDK (@agentmail/sdk) wraps the same operations (accounts.create, messages.send/list/get, attachments.getUrl, webhooks.create, karma.getBalance) and raises a typed AgentMailError carrying an HTTP status and a machine-readable code such as INSUFFICIENT_KARMA or NOT_FOUND.

Use it when an AI agent needs a real inbox or outbox for account signups, verification flows, or transactional back-and-forth email, when you need to provision AgentMail accounts, send messages, read inbox contents, or register inbound webhooks, or when you need to monitor karma usage or wire email events into agent automation.

curl -X POST https://api.theagentmail.net/v1/accounts \
  -H "Authorization: Bearer am_..." \
  -H "Content-Type: application/json" \
  -d '{"address": "my-agent@theagentmail.net"}'

Input: an API key (am_...) plus, per call, an account/message/webhook ID and a JSON body (message fields, webhook URL, etc.). Output: JSON envelopes such as {"data": {"id", "address", "displayName", "createdAt"}} for accounts, message and attachment objects with direction (inbound/outbound), status, and timestamp, a signed download URL for attachments, and {"data": {"balance", "events"}} for karma. Two common polling patterns in the docs are waiting for a verification email by subject match and waiting for an inbound reply after sending, both done by repeatedly listing messages until a match appears.

A full REST surface (accounts, messages, attachments, webhooks, karma) at api.theagentmail.net, plus a TypeScript SDK over the same endpoints. Inbound email can be pushed in real time via a registered webhook, verified with HMAC-SHA256 against a shared secret.

AI agents and their developers that need a disposable but reputable real email identity - to sign up for third-party services and retrieve verification codes, or to hold transactional email conversations programmatically.