The apps
One app you can add to a phone's home screen, with a page per message and a tests page inside it. It is served by the API and show only what the operations return; a key pasted once stays on the device.
https://api.emailimport.com/app/— your mail as a flow: what came in, which bucket took it, what became of it, where it went; your buckets with their addresses; what needs a person.https://api.emailimport.com/app/message/?id=…— one message, all the way through: what arrived (sender, auth, flags, retention), the routing (bucket, matched path, state, deliveries, open tasks), the extraction (every schema field with its value, confidence and where it was read), the text the engine reads with the read values marked, each attachment's text and, for a PDF or image, the file itself, and the original as a reader would see it (framed with scripts stripped and no network). It is also where you correct: type the right value against a field, or select it in the text and name the field. The value is set on the capture (set_field), and the engine answers with the rules that would have read it from where it sits (suggest_extractor); one tap proposes and approves them, so the bucket learns and this message becomes a test case (propose_schema,approve_proposal). Corrections are made against the text the engine reads, since that is what a rule sees; the original is beside it for the eye. Open a message from the flow's incomplete list or from a task.- The same view inside your agent's client (MCP Apps):
get_messageandget_capturecarry_meta.ui.resourceUri = ui://mximp/message, so a client that supports the MCP Apps extension (io.modelcontextprotocol/ui: Claude web and desktop, ChatGPT, VS Code Insiders, Goose) renders the message view in the conversation after either call. It runs in the client's sandbox with no key of its own and no network: every button is atools/callrelayed over your agent's connection (set_field,suggest_extractor,propose_schema,approve_proposal,approve_capture,resolve_task,reprocess_message), and the original is read as the resourcemximp://messages/{id}/original.html. A teaching done there is announced back into the conversation so the agent knows. Clients without the extension ignore the metadata. - Tests (
https://api.emailimport.com/app/tests/) — the regression suite, a page of the same app: cases by bucket, run them now, promote a capture, retire a case, past runs with their failures.
Install
- iPhone: open
https://api.emailimport.com/app/in Safari, Share, Add to Home Screen. Open it from the home screen; notifications work only from there. - Android: open it in Chrome, menu, Add to Home screen (or Install).
- Desktop: the address bar's install icon in Chrome or Edge.
On first open, paste a tenant key; it opens that tenant, tests included, and stays on the device.
Notifications
Turn on notifications in the app to be told, on that device, when mail needs a person (a held capture, a field that requires a human, a forwarding confirmation with its code). Push is delivered through the browser's push service; the payload is encrypted so that service sees nothing.
Incomplete
Messages nothing has received yet, each with why: a delivery that failed and the error the destination gave, a bucket with no destination, no bucket. Tasks that need a person are under Needs you.
Buckets and addresses
Each bucket is listed with where it delivers (a destination with a view_url is a link to the receiving system's own page), the addresses made for it (create_address with bucket), a copy button for handing one to a sender, and the last 30 days of activity: messages, auto-applied, held, last received. + address creates a new one for that bucket from the phone.
Tests
The same suite an agent runs with run_tests before a schema change. Each bucket shows its cases (origin, tricky or not, the expected values), the last run, and a Run now that runs them against the bucket's current schema and shows every failing field as expected → actual. Promote a capture lists recent captures that are not cases yet, held and changed ones first, because a suite of easy cases proves nothing. Retire asks for a reason and calls remove_test.
The operator app
Operator key only. Tabs: Flow (the platform Sankey, requests by surface, interest), Feedback (grouped by triage status, with Discussed / Accept / Decline and a note), Tenants (kind, keys, ingests, and a health panel per tenant: counts and recent ingests, never content), The door (handle exceptions waiting for a decision, and addresses refused at the door). Feedback, interest and exception reasons are text written by strangers and agents; the app shows them as data and a triage status records a discussion, not an approval to act.
The flow
Four stages read top-left to bottom-right: in (each address, the catch-all, uploads), bucket, outcome (auto-applied, approved by a person, held with the reason, unrouted), out (delivered to a webhook, delivery failed, held for reading). Hover or tap a ribbon for its count. The window is 24 hours, 7 days or 30 days.
get_flow returns the same nodes and links over MCP and HTTP, for an agent that wants the picture in numbers.
This page as Markdown.