Skip to content
~/drains.watch_
Soon

Use Drain Watch with your AI

Every incident is plain static data. Give your agent the instructions below and it will watch Drain Watch on a schedule, check whether new drains touch your wallets, and only ping you when one does.

One prompt to set up monitoring

Polls /changes.json at most hourly with ETag requests, reads each changed incident, checks it against your public wallet addresses, extensions and dapps, and alerts you only when it matters.

Endpoints

Changes (JSON)

Every timeline update across all incidents, newest first. The best thing to poll.

https://drains.watch/changes.json
open

Incidents (JSON)

All incidents with severity, threat status, chains, method and links to the full record.

https://drains.watch/incidents.json
open

RSS feed

The same updates as RSS, for feed readers, Slack/Discord/Telegram RSS bots and agents.

https://drains.watch/feed.xml
open

llms.txt

A plain-text map of the site and its endpoints for LLMs.

https://drains.watch/llms.txt
open

Per incident: https://drains.watch/i/<slug>.json (full record + a Markdown agentBrief). Drain methods: /methods.json. All endpoints send CORS * and cache for 60s.

Per-tag feeds

Only want alerts for what you use? Every chain, method, wallet and channel has its own JSON and RSS: /t/<tag>.json and /t/<tag>/feed.xml, plus its own llms.txt.

Copy instructions on every page

Every list and incident page has a Copy brief for your AI button with a preview of the exact text. It copies a Markdown brief (what happened, who's at risk, the drainer domains and addresses to block, what to do now, how to avoid it, sources) that you can paste into ChatGPT, Claude or any agent.

Brief for your AI


Get notified about new drains

Follow every new drain and update in your feed reader, Slack, Discord or Telegram RSS bot:

Only follow a chain or a method you care about: every tag has its own feed at /t/<tag>/feed.xml.

Copied