Your docs drifted from your code.
docsParity finds where.
Give it a GitHub repo and a docs URL. It pulls the real exported API surface, crawls the documentation, and shows you exactly where they no longer match — ranked by severity, each with the fix.
Why docs drift is expensive
A developer clones a popular SDK, follows the docs, and hits an error because a method signature changed three months ago — but nobody updated the docs. Two hours gone. docsParity catches that mismatch in about 30 seconds, before it costs anyone an afternoon.
- 30s
- From two URLs to a ranked report
- /10
- A deterministic, shareable drift score
- 1-click
- File the fix as a GitHub issue
How it works
Read the real API
We pull entry points and key source files, then parse them with the TypeScript compiler (TS/JS) or a signature extractor (Python) — not regex.
Crawl the docs
Firecrawl scrapes the documentation site to clean Markdown — the text developers actually read.
Diff with Claude
Claude compares signatures, exports and config against the docs and returns the top mismatches, each with a suggested fix.
What every report gives you
- Side-by-side mismatches
The exact code snippet next to the conflicting docs snippet, so you can see the drift at a glance.
- A drift score out of 10
Deterministic and reproducible — computed from severity-weighted findings, not a number the model guessed.
- A suggested fix per finding
Corrected docs text you can paste straight in.
- A shareable permalink
Every run gets its own URL and social card. Post your score.
- Submit to maintainer
One click opens a pre-filled GitHub issue with the formatted report.
- Full transparency
See which files were inspected, how many symbols were extracted, and which model ran.