ObsolotAPI deprecation tracking across every repository you own
Deprecating an API is easy. Knowing when it is safe to delete is not.
Obsolot tracks a deprecated API the whole way: who still calls it, in which repositories, how that number is trending, and whether the end-of-life date you published is realistic.
Announce with an end-of-life date that means something
Each API deprecation is a notice with an end-of-life date, markdown migration guidance, and search patterns describing the call sites. The date is attached to the same record that tracks the remaining callers, so "we're removing this in March" is a claim you can check rather than a hope.
Find the callers you didn't know about
Code-search jobs run against your configured GitHub and GitLab integrations and return file-and-line references for the patterns the notice defines. Callers in repositories you'd forgotten about show up the same way as the ones you expected.
Progress is then tracked per repository, which is usually how the work is actually owned and scheduled.
Let the migration be proposed for you
An AI agent classifies each reference — is this a real call, a comment, a test fixture, a false positive? — and drafts a migration for the ones that matter. Every proposal goes to a review queue for a human to approve or reject before anything is acted on.
Give AI coding agents the context they lack
Coding agents that don't know an API is deprecated will happily write new calls to it. Obsolot exposes its notices and code references over the Model Context Protocol, so an agent can ask what's deprecated, retrieve the migration guidance, and propose fixes in real time — see deprecation context for AI coding agents.
Ready to see your own call sites? Pricing starts free.