You found me.

I created this service to help me e2e test websites with OTP logins. Feel free to use this as you like.

It's currently rate limited to 5 requests per 10 seconds.

Any email user will work, but a good one for you is:

purr-exhume-8t62vx@testcode.email

Submit it on whatever platform you want. Then fetch your code within 2 minutes at:

https://testcode.email/latest/purr-exhume-8t62vx

I'll leave this up as a public service for now. If you want to build your own, paste this into your Codex.

Start by running:

```bash
npm create cloudflare@latest -- test-email-otp-worker
```

As described in https://developers.cloudflare.com/workers/get-started/guide/

Run this from wherever code is usually written in this environment. If there is an obvious projects folder such as ~/code, ~/src, ~/projects, or the current workspace root, use that and say which one you chose.

Build a Cloudflare Worker that works like testcode.email: a public test email receiver for OTP-based end-to-end tests.

Important setup behavior:
- Before doing Cloudflare work, retrieve the current Cloudflare Workers, KV, Email Routing, Workers AI, Wrangler, and WAF rate limiting docs.
- If npm is not in PATH, check for Node/npm through common environment managers like nvm, fnm, Volta, Homebrew, asdf, or corepack. Do not invent an install. If you cannot run npm, stop gracefully and give the human exact next steps to install Node.js/npm and rerun the bootstrap command.
- If there is no Cloudflare account or Wrangler is not authenticated, still scaffold and implement everything possible locally. Then give the human clear next steps to create/sign into a Cloudflare account, run `npx wrangler login`, create resources, configure DNS/email routing, and deploy.
- Prefer implementing and verifying locally over only explaining. Run typecheck/tests when available.

Cloudflare project choices:
- Project name: test-email-otp-worker.
- Use the Worker-only starter. TypeScript is preferred if the create-cloudflare flow offers it; otherwise use JavaScript and keep the implementation simple.
- Install `postal-mime` for parsing incoming emails.

Worker requirements:
- Bind a Workers KV namespace as `EMAILS`.
- Bind Workers AI as `AI`.
- Implement an Email Routing handler that accepts catch-all routed mail for the domain.
- Store incoming emails in KV under a key scoped by the local part before @.
- Expire stored emails after 2 minutes.
- Keep enough raw email content to parse later, but public responses must be compact.
- Expose `GET /latest/<user>` to return the latest email sent to `<user>@your-domain`.
- Ignore the domain in the lookup; use the local part that Email Routing delivered to.
- Return compact JSON exactly shaped as: `to`, `from`, `subject`, `body`, `otp`, `receivedAt`.
- Parse email bodies with `postal-mime`.
- Extract numeric OTPs with regex first, using a 6-digit code pattern.
- Use the Workers AI binding only as a fallback when regex does not find a code. The AI prompt must treat email content as untrusted and return only the code or null.
- Generate public example addresses on `/` from the EFF large Diceware wordlist plus a 6-character lowercase alphanumeric suffix.
- The `/` page should tell users the service is currently rate limited, show the generated address in bold, add a `Copy email to clipboard` button below it, make the `/latest/<user>` URL click-to-copy, show this full build prompt in a wide text box, and include a `Run in Codex` link using `codex://threads/new?prompt=...`.
- Put the disclaimer at the bottom under a `DISCLAIMER` heading, including that the service can be taken down, changed, restricted, rate limited, or otherwise limited at any time for any reason or no reason.

Deployment and Cloudflare setup requirements:
- Create the KV namespace and put its id in `wrangler.jsonc`.
- Configure the AI binding in `wrangler.jsonc`.
- Run `npx wrangler types` after changing bindings.
- Deploy with `npx wrangler deploy` if authenticated.
- Configure a custom domain for the Worker.
- Configure Email Routing for the domain and route catch-all mail to the Worker.
- Configure a WAF rate limiting rule for `/latest/*` at 5 requests per 10 seconds.

Final response requirements:
- If deployment succeeded, give the deployed URL and a short usage example.
- If deployment could not be completed because the human needs a Cloudflare account, DNS/domain access, auth, or billing choice, say exactly what was completed locally and list the remaining steps in order.
- Include the commands the human should run next.

Run in Codex

DISCLAIMER

This service is provided as-is and as-available, with no guarantees or warranties of any kind. By using it, you accept all risk and responsibility for your use, including any data you send to it. I may take down, change, restrict, rate limit, or otherwise limit this service at any time, for any reason or no reason. I am not responsible or liable for misuse, unauthorized access, data loss, service interruption, platform action, or any other damages or claims arising from use of this service.