WatchFox

The email watch API that catches what you want and gives you

Email

Developer Tools

Artificial Intelligence

GitHub

Visit WebsiteSee on Product HuntGithub ⧉

Hi Product Hunt 👋 I'm Seth, the maker of WatchFox. Every team that wants to "react to inbound email" ends up writing the same fragile pile: IMAP polling, regex rules, an LLM prompt per email, and a privacy question nobody can answer ("where did our customers' emails go?"). WatchFox replaces that with one API call. You say which mailbox to watch and what to catch (enquiries, invoices, support tickets, purchase orders, job applications, claims, or a type you define). When one arrives, your server gets a signed webhook. What's different: 🧠 An open-weights decision model, not a chat LLM. Emails are judged by a small encoder (421M parameters) that gives calibrated yes/no scores. No per-email token bill, no invented answers, and the text of a customer's email never goes to a closed AI API. 🫥 It forgets. We keep the subject, sender, a 300-character snippet and the scores (for 90 days). The full email and attachments are read from the mailbox at the moment you ask for them, streamed to you, and never stored. 🎯 Types that tune themselves. Describe a new type and give some examples; WatchFox tries several wordings of the question, picks the one that separates your examples best, and sets the threshold. Press "wrong catch" on a real email and it learns from the mistake. 🔌 Built for developers and their AI agents. Branded "connect your mailbox" page for your own customers, signed webhooks with retries, and docs that coding agents can read from one file (/llms-full.txt). Honest limits: this first release covers email only, and the built-in types are tuned on a small set, so please check them on your own mail before you rely on them. There is a free plan (50 runs a month) and a sandbox mailbox so you can try everything without connecting real email. I'd love your help: what inbound-email event would you want caught first? And I'm happy to answer anything.