Everything E-mail gives you
- 01
Every message, kept
HTML, text, headers and attachments of every message, filtered by recipient, subject, kind, language or inbox.
- 02
Codes and links extracted
Built-in code, links and attachments extractors, plus your own regex, CSS selector or header rules.
- 03
Inboxes that decide
An inbox accepts, bounces, defers N times, holds or drops what lands in it; temporary inboxes expire by themselves.
- 04
Steps after delivery
Inbox steps open the message or click a link after a wait, with jitter, so tests never wait for a person.
- 05
Act as the recipient
Open, click, spam report or unsubscribe sends SendGrid's Event Webhook, signed with ECDSA, to your app.
- 06
Hold and decide
A held message waits for you: deliver, defer, bounce hard or soft, or drop; the app gets the matching event.
- 07
Strict or unreachable intake
Validate keys (401, or 535 on SMTP), drop STARTTLS, refuse recipients with 550 or 451, or time out.
- 08
Wait, or expect none
wait_for_message returns the extracted value; expect_no_message passes only if nothing arrives in time.
The screens
Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.
The message, and what was pulled out of it

A test made this address; it expires by itself in 18 min.
Via the SendGrid API or SMTP, with sender, recipient, time and trace.
Your extractor found the OTP; wait_for_message with extract returns it.
Every link is detected; short links can be followed to the final URL.
Delivery and recipient events sent to the app's Event Webhook.
- Temporary inbox
A test made this address; it expires by itself in 18 min.
- How it came in
Via the SendGrid API or SMTP, with sender, recipient, time and trace.
- Extracted code
Your extractor found the OTP; wait_for_message with extract returns it.
- Links
Every link is detected; short links can be followed to the final URL.
- Events
Delivery and recipient events sent to the app's Event Webhook.
An inbox decides what happens on arrival

Made by a test over the API; extend it or keep it with the environment.
Hard bounce, 550 mailbox unavailable, as the provider's event.
Defer 3 times, then accept: tests the app's retry.
Decide by hand with decide_held, or let the steps decide.
Delivered, opened 30 s later with 5 s of jitter, click signLink: no person needed.
- Temporary
Made by a test over the API; extend it or keep it with the environment.
- Bounce it
Hard bounce, 550 mailbox unavailable, as the provider's event.
- Defer N times
Defer 3 times, then accept: tests the app's retry.
- Hold it
Decide by hand with decide_held, or let the steps decide.
- Automatic steps
Delivered, opened 30 s later with 5 s of jitter, click signLink: no person needed.
Extractors, tried before you save

Subject, text, HTML, link, header or attachment.
A regex, CSS selector or header name; a capture group becomes the value.
For short links: the value is the final URL.
test_extractor runs the rule on recent mail: matched, skipped, no such link.
Messages where the rule found nothing, with the reason and a suggested fix.
- Take it from
Subject, text, HTML, link, header or attachment.
- Rule
A regex, CSS selector or header name; a capture group becomes the value.
- Follow redirects
For short links: the value is the final URL.
- Against the last 50
test_extractor runs the rule on recent mail: matched, skipped, no such link.
- Why not
Messages where the rule found nothing, with the reason and a suggested fix.
Break it on purpose
The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.
BounceHard or soft; the app gets the bounce event
decide_held {action: bounce, kind: hard}Defer, then acceptThe message is deferred N times before delivery
create_inbox {on_arrival: defer, defer_times: 3}DroppedThe provider refuses to send it
decide_held {action: drop}Spam reportThe recipient marks it as spam; signed event to the app
simulate_recipient {action: spamreport}UnsubscribeThe recipient unsubscribes; signed event to the app
simulate_recipient {action: unsubscribe}Provider unreachableThe intake times out, refuses, or answers 503 or 429
set_access {how: timeout}TLS troubleSMTP without STARTTLS, or a TLS failure
set_access starttls / how: tlsRecipients refusedSMTP answers 550 or 451 to RCPT TO
set_access {refuse_recipients: 550}Revoked keySends get 401, or 535 on SMTP, while keys are validated
revoke_key
Why not the real sandbox
Nothing leaves the machine
Mail to any domain is caught and never reaches a real inbox, so tests can use any address.
Bounces on demand
Hard and soft bounces, defers and drops happen when the test asks, not when a real server feels like it.
Values, not HTML scraping
Tests ask for extract=otp or a link and get the value; the extractor shows why a message did not match.
Throwaway inboxes
Each test makes its own inbox that expires on its own, so parallel runs never read each other's mail.
Your AI agent drives it
Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.
Test the password reset e-mail end to end and get me the reset link.
MCP tools
list_messagesMessages with filters, or grouped by kindget_messageHeaders, text, HTML, extracted values, eventswait_for_messageWait for a message; with extract, return the valueexpect_no_messagePass only if nothing arrives in timecreate_inboxA temporary or kept inbox with its rule and stepsdecide_heldDeliver, defer, bounce or drop a held messagesimulate_recipientOpen, click, spam report or unsubscribetest_extractorRun a rule on one message or the last Nset_accessMake the intake strict or unreachable
The same over HTTP
- GET
/api/messages - GET
/api/messages/wait - POST
/api/inboxes - POST
/api/messages/{id}/decide - POST
/api/messages/{id}/events
- SMTP uses a self-signed certificate for STARTTLS; SendGrid is served on 8025.
- Extractors live in email/extractors.yaml and also work for SMS.