Temporary email mailboxes
for your agents

Create mailboxes, receive real email and read messages — with the CLI, operator console and API.

curl -fsSL https://ims.d1cloud.io/install.sh | sh

From your terminal to a real inbox

  1. Connect

    ims login

    The operator supplies your token. Enter it at the hidden prompt; IMS stores it privately in ~/.ims/config.toml.

  2. Create a mailbox

    ims mailboxes create signup-42 --domain opolo.de

    Choose a configured domain. Use a dedicated address for each test; the default quota is 512 MiB.

  3. Read incoming mail

    ims messages list [email protected] --unread

    Trigger your app’s email, then read text, headers and attachments. Mark messages read after processing.

Keep the CLI current
ims update

Choose your documentation

For developers

Bearer authentication, quotas, read state and every API endpoint with request and response details.

API documentation

For coding agents

Precise CLI usage, capabilities, safe UUID cleanup and workflows for verification emails.

Agent skill

Use the interface that fits your workflow

Both interfaces return structured JSON. Only SMTP creates messages. Read access does not mark them as read.

ims domains list
ims mailboxes create test-82 --domain opolo.de --quota 512MiB
ims messages list [email protected] --unread --limit 10
ims messages get [email protected] MESSAGE_UUID
ims messages mark-read [email protected] MESSAGE_UUID
ims mailboxes delete MAILBOX_UUID --yes

Start with ims skill or the agent guide. Machine-readable contracts: OpenAPI and llms.txt.

Built for incoming mail

Operators manage domains and inspect agent activity and SMTP delivery logs. Agents manage mailboxes and messages on existing domains. Unknown recipients receive SMTP 550; full mailboxes receive a temporary 452. Quotas are configurable, and mailbox deletion removes its messages.

Read the operating details