One endpoint, three ways in
Paste HTML in the app, forward campaign mail to your dedicated ingest address, or POST directly to /v1/tests. All three land in the same pipeline.
Product
Email QA your delivery pipeline can call.
Create tests from HTML or raw MIME, then stream per-client results back to a person, a CI job, or an MCP-enabled agent.
Progressive preview matrix
Each client reports queued, processing, done or failed as its render completes, streamed over SSE — so the grid fills in rather than blocking on the slowest client.
Sharing built for email work
Private, no-index share links with a time-to-live picked at creation, an optional password, and a hard delete of the page and its assets when the link lapses.
MCP-native
An agent can create a test, inspect per-client status, retrieve previews and close the loop on broken markup without a human relaying screenshots.
The MCP server
Five tools, so an agent can test its own output.
- create_test
- Submit HTML or raw MIME and start the fan-out.
- get_test_status
- Per-client state for one test.
- get_preview
- The rendered screenshot for one client and mode.
- list_client_profiles
- What the account is entitled to render.
- create_share_link
- A private, expiring URL for a stakeholder.
Served over Streamable HTTP alongside the REST API, so the same account and the same API key drive both.
Get started