Keep your API docs current.
Your API surface changes every release. uptodate reads the diff, works out which endpoints, parameters, and examples the change made wrong, and opens a pull request with the correction before your integrators hit it.
Renamed and removed params
A field gets renamed, a query param disappears, a response shape changes. The reference still documents the old one until someone notices.
Stale request and response examples
Copy-paste examples are what developers actually use. When the payload changes, every example that hardcoded the old shape is now wrong.
Endpoints that no longer exist
Deprecated routes linger in the docs long after the code drops them, sending integrators down paths that return 404.
The fix arrives as a pull request
uptodate never edits your published reference directly. It drafts the change against your docs in git, so you review the diff next to the code that caused it and merge when it is right. Your docs host picks up the change on its own.