You have sent a test email and want a second pair of eyes: does the subject fit, are all links absolute and alive, is the unsubscribe link there, is the text readable when images are blocked? Asking a human costs a round trip. An AI assistant answers in seconds — if you hand it the email in a format it can actually read.

Do not paste screenshots — share the machine-readable view

Copy-pasting from a browser loses the headers, the plain-text part and the attachments, and screenshots lose everything else. Instead, use the read-only share link of the inbox: a human opens it in the browser, and an assistant reads the same content as data.

How the export works

Take the share link (/s/…) and append /export:

  • /s/…/export — JSON with every captured item (default).
  • /s/…/export?format=text — a plain-text digest, ideal for pasting into a prompt.

The JSON looks like this (trimmed):

{
  "resource": "inbox",
  "name": "Staging app",
  "read_only": true,
  "generated_at": "2026-09-10T12:00:00+00:00",
  "expires_at": "2026-09-11T12:00:00+00:00",
  "count": 2,
  "items": [
    {
      "id": 17,
      "from": "App <app@example.com>",
      "to": ["customer@example.com"],
      "subject": "Your invoice #1042",
      "received_at": "2026-09-10T11:58:00+00:00",
      "text": "Hello! Your invoice is attached.",
      "attachments": [{"filename": "invoice.pdf", "contentType": "application/pdf", "size": 18422}]
    }
  ]
}

Webhook shares answer with the request itself: method, URL, query, headers, raw body, IP, user agent and time.

A prompt that works

Fetch https://sandbox.example.com/s/TOKEN/export?format=text and review the emails.
Check: subject under 60 characters and not ALL CAPS; every link absolute and
reachable; an unsubscribe link present; no placeholder text like "Lorem" or
"{{name}}"; plain-text version readable without images.
Answer with a checklist of problems and a suggested fix for each.

Because the export includes the plain-text part, the model can judge both versions of the email without rendering anything.

Safety rules

  • The share link is the credential: treat it like a password. Set the shortest acceptable expiry (one hour is often enough) and revoke it when you are done.
  • Send test data only. The sandbox never delivers real mail, but an assistant can still forward what you give it.
  • The link is read-only and every response carries noindex, so crawlers will not store your test message.
  • The export is capped to the latest items, so a busy inbox cannot return unlimited data.

Automate it in CI

curl the export, then assert on it with your test runner, or pipe it to your own model call and fail the build when the checklist is not empty. It is the same endpoint your assistant uses — one implementation for humans, scripts and models.

Next steps