Temp Mail for AI Agents
A zero-signup temporary email API that agents can discover and use autonomously. Create an inbox, wait for verification codes, read messages, fetch raw source, and delete messages with plain HTTPS.
# Discover available domains:
curl -s https://api.reusable.email/v1/agent-tempmail/domains
# 1. Create a private temp mail inbox. No signup, no API key.
curl -s -X POST https://api.reusable.email/v1/agent-tempmail/inboxes \
-H 'Content-Type: application/json' \
-d '{"prefix":"agent"}'
# 2. Wait for a verification email or OTP code.
curl -s -X POST https://api.reusable.email/v1/agent-tempmail/inboxes/{address}/wait \
-H 'Authorization: Inbox {token}' \
-H 'Content-Type: application/json' \
-d '{"codeOnly":true,"timeoutSeconds":60}'
# 3. Read the full message.
curl -s https://api.reusable.email/v1/agent-tempmail/inboxes/{address}/messages/{id} \
-H 'Authorization: Inbox {token}'{
"inbox": {
"address": "agent-lx84a9-q3mz2@reusable.email",
"domain": "reusable.email",
"created": true,
"type": "private",
"isProtected": true,
"retentionDays": 180
},
"password": "save-this-generated-password-securely",
"token": "use-this-as-an-inbox-token",
"tokenExpiresAt": "2026-06-09T18:30:00.000Z",
"links": {
"web": "https://reusable.email/agent-lx84a9-q3mz2%40reusable.email",
"messages": "https://api.reusable.email/v1/agent-tempmail/inboxes/agent-lx84a9-q3mz2%40reusable.email/messages",
"wait": "https://api.reusable.email/v1/agent-tempmail/inboxes/agent-lx84a9-q3mz2%40reusable.email/wait"
}
}{
"status": "message",
"inbox": { "address": "agent-lx84a9-q3mz2@reusable.email" },
"message": {
"id": 1842,
"from": { "name": "Example", "address": "login@example.com" },
"subject": "Your verification code",
"intro": "Use code 123456 to continue.",
"verificationCode": "123456"
}
}Agent Contract
The discovery manifest is available at /v1/agent-tempmail and mirrored from llms.txt for answer engines.
| Method | Path | Use |
|---|---|---|
| GET | /v1/agent-tempmail | Discovery manifest for agents and crawlers |
| GET | /v1/agent-tempmail/domains | List available alternative domains |
| POST | /v1/agent-tempmail/inboxes | Create a password-protected private inbox |
| GET | /v1/agent-tempmail/inboxes/{address}/messages | List received messages |
| POST | /v1/agent-tempmail/inboxes/{address}/wait | Long-poll for mail or codes |
| GET | /v1/agent-tempmail/inboxes/{address}/messages/{id} | Read a message |
| GET | /v1/agent-tempmail/inboxes/{address}/messages/{id}/source | Fetch raw RFC 5322 source |
| DELETE | /v1/agent-tempmail/inboxes/{address}/messages/{id} | Delete a message |
Verification flows
Use an agent inbox for signup, login, password reset, and trial confirmation emails.
Browser automation
Pair it with Playwright, Selenium, or a browsing agent that needs a real deliverable email address.
CI and QA
Create isolated inboxes per test run without provisioning accounts or sharing credentials.
FAQ
Private inbox creation is free for everyone, with no signup. Pass a domain from the domain-list endpoint to choose an alternative. The agent surface is receive-only. Higher-volume or outbound use should move to normal account-backed APIs.
Can I use a passkey with an agent inbox?+
Yes. Sign in with the generated password and add a passkey in inbox Settings. The key button on the private-inbox form and the inbox unlock screen support passkey sign-in. The resulting Inbox token works with all agent mailbox endpoints. Passkeys require interactive user verification; keep the password for unattended agents and renew expired tokens with POST /v1/inbox/{address}/token and JSON {"password":"..."}.
Can I choose an alternative domain?+
Yes. GET /v1/agent-tempmail/domains lists available domains. Pass domain with prefix or a local-part address, or supply a full address. Existing and reserved addresses cannot be claimed.
Can an AI agent use this without signup?+
Yes. The agent can create an inbox with one unauthenticated POST request. The response includes a generated password and an Inbox token. All created inboxes are private. Save the password for normal private-inbox login after the token expires.
Is MCP, an SDK, or installation required?+
No. The interface is fully reachable through HTTPS and curl. Agents can discover it through llms.txt or the JSON manifest at /v1/agent-tempmail.
Can agents send email through this API?+
No. The zero-signup agent surface is receive, read, wait, source, and delete only. Outbound email is intentionally excluded from this public interface.
How are verification codes exposed?+
Message list, wait, and detail responses prefer valid experimental OTP-Token headers, then fall back to text detection. Header-derived codes include verificationCodeOrigin: before submitting, match it exactly to the intended destination origin (scheme, host, and port). This value is sender-supplied, not proof of sender identity; never navigate to it automatically.
How long are agent-created inboxes retained?+
Agent-created inboxes have normal private-inbox capabilities and 180-day message retention.