Skip to content
Inlet

Documentation

How to set up a check, what each result means, and where the safety boundaries are.

Set up a check

  1. Add the exact page that holds your form and confirm you control the website.
  2. Connect the destination: an IMAP mailbox read-only, or a signed inbound endpoint.
  3. Let Inlet propose a field mapping and correct anything it got wrong.
  4. Optionally connect a repository or upload a source archive so failures can be investigated.
  5. Run the first check, then set a schedule. The shortest interval is 15 minutes.

Destinations

A provider accepting a message is not the same as the message arriving, so Inlet only counts what it can find at the destination. IMAP access is read-only and limited to the folder you choose. Inbound endpoints must send an HMAC signature and a recent timestamp.

Result definitions

Received
The browser submitted the test and the same unique ID was found in the destination.
Not received
The submission happened, the destination was reachable, and nothing matching arrived during the observation window.
Unverified
The destination could not be reached or the submission could not be confirmed. Inlet makes no claim either way.
Browser failed
Navigation, a field or the submit control failed before a credible submission.
Patch ready
A patch inside the allowed files passed every required check and delivered a message in a private preview.
Verified recovered
After deployment, a new browser run produced a new message at the destination.

Safety

  • Every browser and repair run uses a new container with a read-only filesystem, no Linux capabilities, and CPU, memory, process and time limits.
  • Containers can only reach the network through a gateway that allows the verified website. Everything else is refused and logged.
  • The model can only call a fixed list of tools. Website text, repository files and emails are treated as untrusted data.
  • Patches cannot change tests, dependency manifests, CI, or environment files. Nothing is merged or deployed by Inlet.

FAQ

Can Inlet test any website?

Only websites you confirm you control, by DNS TXT record or an HTML meta tag. CAPTCHA-protected forms need a different test route because Inlet does not try to bypass them.

Which code can it repair?

Next.js and Node.js handlers with a testable mail adapter are the supported stack. If the cause is outside the code, you get a diagnosis and what to check next.

What reaches the AI model?

Sanitized run evidence and files in the paths you approved. Environment files and credentials are removed before anything is read, and no credentials ever enter a browser or repair environment.

Run the live example to see a check from start to finish.