What is Reusable.Email?

Reusable.Email is a disposable email service that lets you create temporary email addresses instantly — no signup, no forms, no verification required. Unlike traditional temp mail services that auto-delete after minutes, Reusable.Email offers reusable addresses with retention from 90 to 365 days. Use public inboxes for quick verifications, private inboxes with password protection for sensitive signups, or managed inboxes with full IMAP/SMTP support for a permanent disposable address that works with any email client.

Is Reusable.Email free?

Public and private inboxes are completely free with no limits on usage. You can create unlimited free inboxes without any account or payment. For advanced features, managed inboxes cost a one-time $3 payment (not a subscription) and include IMAP/SMTP access, send capability, and 365-day retention. Custom domains are free to add with DNS verification — $10/year unlocks unlimited aliases and catch-all routing. Whitelabel plans at $30/month are available for businesses needing their own branded email infrastructure. There are no hidden fees, ads, or subscription traps.

How long are emails retained?

Email retention depends on your inbox type. Public inboxes retain emails for 90 days from receipt — enough for most verification and signup workflows. Private (password-protected) inboxes extend retention to 180 days, giving you more time to access important emails. Managed inboxes offer the longest retention at 365 days with unlimited storage, plus the ability to organize emails into custom folders. All inbox types allow you to export your data at any time. Emails are automatically and permanently deleted after the retention period expires.

Can I send emails from Reusable.Email?

Yes — sending is available with managed inboxes ($3 one-time payment). Managed inboxes include full SMTP access via smtp.reusable.email on port 587 with STARTTLS encryption, allowing you to send email to any address worldwide from any standard email client including Apple Mail, Thunderbird, Outlook, and Gmail. Free public and private inboxes support sending only to other Reusable.Email addresses. Custom domain users can also send as their domain aliases, with SPF, DKIM, and DMARC authentication configured automatically.

How does custom domain support work?

Adding a custom domain to Reusable.Email is free — you configure the DNS records we provide (MX, SPF, DKIM, and DMARC) and we verify your domain automatically. Once verified, all email sent to any address at your domain is routed to your managed inbox. Subscribe for $10/year to unlock unlimited aliases (sales@, support@, info@ etc.), catch-all routing that captures email to any address at your domain, and send-as capability from any alias. Custom domains eliminate blocklist issues entirely since you control the domain reputation.

What is a managed inbox?

A managed inbox is a permanent, full-featured email address on Reusable.Email. For a one-time $3 payment (no subscription), you get IMAP access via imap.reusable.email:993 and SMTP access via smtp.reusable.email:587, enabling use with any standard email client — Apple Mail, Thunderbird, Outlook, or any app that supports email account setup. Managed inboxes include the ability to send email to any address worldwide, 365-day email retention, unlimited storage, spam filtering, custom folder organization, and the ability to toggle between public and private visibility modes.

Privacy depends on your inbox type. Public inboxes are visible to anyone who knows the address — they are designed for non-sensitive use like quick verifications. Private inboxes add password protection so only people with the password can access the emails. Managed inboxes are password-protected and offer additional security through standard email authentication protocols. Reusable.Email does not sell user data, does not serve advertisements, and does not track users across websites. Analytics are privacy-focused with IP tracking disabled and email addresses sanitized from all tracking data. Payments are processed securely through Stripe.

Can I use my own email client?

Yes. Managed inboxes support standard IMAP and SMTP protocols, making them compatible with virtually any email client. Connect using imap.reusable.email on port 993 for receiving and smtp.reusable.email on port 587 for sending, both with STARTTLS encryption. This works with Apple Mail, Mozilla Thunderbird, Microsoft Outlook, Gmail (via 'add account'), K-9 Mail on Android, and any other application that supports standard email account setup. Your managed inbox credentials are generated automatically when you upgrade.

Agent-ready temp mail

Temp Mail for AI Agents

Name: Reusable.Email
Brand: Reusable.Email
Availability: InStock

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.

No signupNo API keyNo MCP installCurl traversable

Quickstart

# 1. Create a public 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}'

Create response

{
  "inbox": {
    "address": "[email protected]",
    "domain": "reusable.email",
    "created": true,
    "retentionDays": 90
  },
  "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"
  }
}

Wait response

{
  "status": "message",
  "inbox": { "address": "[email protected]" },
  "message": {
    "id": 1842,
    "from": { "name": "Example", "address": "[email protected]" },
    "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
POST	`/v1/agent-tempmail/inboxes`	Create or ensure a public 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

The public agent surface is intentionally receive-only. Higher-volume or outbound use should move to normal account-backed APIs.

Can an AI agent use this without signup?+

Yes. The agent can create an inbox with one unauthenticated POST request. The response includes an Inbox token for read, wait, source, and delete operations.

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 include verificationCode when a likely OTP, PIN, or login code is detected in the subject or preview text.

How long are agent-created inboxes retained?+

Agent-created inboxes use normal public inbox retention. Messages are retained for 90 days unless deleted earlier.