ID-Bot continuously monitors breach databases and dark web feeds. The moment your credentials surface anywhere on the internet, it acts — before you even know it happened.
ID-Bot monitors the sources that matter — breach databases, leaked credential indexes, and dark web feeds — continuously, without any configuration from you.
Monitors your accounts against the HIBP v3 API. Checks both personal account breaches and the latest public breach disclosures.
Hourly pollScans leaked credential databases for your email addresses, usernames, or domains. Catches breaches not yet in public indexes.
Hourly pollClaude reads any dark web intelligence feed or breach disclosure page via headless browser. No scraping scripts needed.
ConfigurableMonitor security disclosure blogs, threat intel feeds, or vendor breach notification pages. Claude decides what's actionable.
ConfigurablePlug in any external breach notification service via HMAC-verified webhook. ID-Bot responds in seconds, not hours.
PushStill want to catch vendor emails? ID-Bot monitors your inbox too — Claude evaluates every message against your trigger rule.
IMAP pollID-Bot's breach intelligence can drive any autonomous response workflow in a real browser.
Monitor all company accounts across every breach database. Rotate en masse the moment exposure is detected.
Set it once. ID-Bot watches every breach database and rotates passwords on affected sites automatically.
Watch for any new public breach that mentions your domain. Trigger response workflows before employees are notified.
Automate the breach response playbook: detect → rotate → log → notify compliance team — all within minutes.
One ID-Bot deployment monitors dozens of client accounts and domains. Separate vaults and notifications per client.
ID-Bot's trigger layer is general. Add any browser-based response: file a report, provision a service, notify a team.
Pick the model that fits your clients — same platform, different footprint.
Point ID-Bot at your accounts and domains. It finds the breaches, evaluates the risk, and acts — no triggers to define.
{ "name": "Breach Guardian", // ID-Bot monitors breach databases autonomously — no trigger to define "triggers": [ { "type": "breach_intel", "monitored_accounts": ["you@email.com", "work@company.com"], "monitored_domains": ["company.com"], "monitor_latest_breaches": true, "only_new_breaches": true, "match_rule": "rotate credentials if passwords or auth tokens were exposed", "poll_interval_seconds": 3600 } ], // What to do when a breach is found "action": { "goal": "Rotate the password on the affected site and save to vault" }, // How to run it "runtime_mode": "hybrid", "browser_mode": "visible", // Where to send the report "notifications": [ { "channel": "slack", "destination": "#security-alerts" } ] }
ID-Bot is in early access. Request access to get set up with the right deployment tier for your use case.
Request Access →