Botd vs Microsoft Security Response Center (MSRC)

BotD is FingerprintJS's open-source, MIT-licensed JavaScript library that runs entirely in the browser to flag basic automation -- headless Chrome, PhantomJS, Selenium, and similar tools -- without any server round-trip for the detection itself. It ships as an npm package or as a CDN-hosted ES module and returns a plain detected/bot-kind result object from a single detect() call. It is free for any use with no signup; FingerprintJS separately sells a more sophisticated, paid, server-side Bot Detection API for teams that need those extra signals.

MSRC's CVRF API serves Microsoft's own machine-readable security-update bulletins: list every bulletin's ID and dates from `/updates`, then pull one full document by ID (e.g. "2026-Jan") from `/cvrf/{id}` -- as CVRF XML by default, or the same CVRF document serialised to JSON under an `Accept: application/json` header. It's a fully public, unauthenticated REST endpoint with no signup or key required, backing tools like the community MsrcSecurityUpdates PowerShell module. Two traps confirmed live: the OData-shaped response envelope is misleading (most `$filter`/`$top` syntax 500s, and there's no CVE-to-bulletin lookup at all), and the separately documented `/csaf/{id}` route rejected all 17 id formats probed with "Invalid ID format" -- so despite the CSAF branding, the JSON this API actually returns is CVRF, not CSAF. The old stored URL pointed at the unrelated Report Abuse API's developer page; the live developer portal for this security-updates API now redirects straight to its published OpenAPI/Swagger definition.