Deprecation countdowns for the APIs you use

The idea

API providers announce deprecations responsibly and it does not matter, because the announcement lands in a changelog nobody at the affected company reads. Shopify sunsets API versions on a fixed cadence and breaks a wave of apps every time; Stripe, Twilio and Meta do the same on their own schedules. The failure is not information scarcity, it is that no tool answers the only question that matters: is my code affected, and when does it break.

The wedge is the join between two datasets nobody has connected: a curated feed of structured deprecation records, and a scan of your actual repos for the affected endpoints and SDK calls. LLMs make the feed side cheap to build now, changelog parsing was previously a manual editorial job, but the human-review queue stays, because one false alarm ends the subscription.

Who pays

The buyer is an agency maintaining a dozen client Shopify or Stripe integrations, or a SaaS team built on two or three critical third-party APIs, paying 29 to 99 dollars a month. Agencies are the sharper target: a missed sunset in a client’s app is a reputational incident. Distribution through Shopify and Stripe developer communities, plus content that rides each announced sunset wave with a check if you are affected landing page.

MVP scope

• Curated deprecation feed for Stripe, Shopify, Twilio, Google Maps and Meta Graph, LLM-extracted and human-approved
• GitHub App repo scanning with per-deprecation code signatures, weekly and on push
• Dashboard of countdown cards showing only deprecations that hit your code, with file-level links
• Email and Slack alerts at 90, 30 and 7 days
• Admin review queue for feed quality
• Skip for v1: auto-generated migration PRs, GitLab and Bitbucket, self-serve custom API feeds, SDK version-bump tracking

Build SunsetRadar, a web app that cross-references API deprecation announcements against a team's actual code. Stack: Next.js (App Router), a GitHub App for repo access, Postgres via Prisma, Claude API for changelog parsing.

Two data pipelines. First, the deprecation feed: a daily job pulls changelogs and deprecation pages for five APIs at launch (Stripe, Shopify, Twilio, Google Maps, Meta Graph), and Claude extracts structured records: affected endpoint or SDK method, sunset date, replacement, source URL. A human-review queue in an admin panel approves each extracted record before it goes live, because a false alarm kills trust in a tool like this.

Second, code scanning: user installs the GitHub App on repos; a job clones each repo and matches files against per-deprecation signature sets, which are regex and import-aware patterns for REST paths, SDK method names, and pinned API version strings (for Shopify, parse the api_version config specifically). Rescan weekly and on push to the default branch.

The match table joins the two: dashboard shows a countdown card per live deprecation that actually hits your code, expanding to file-and-line links into GitHub, the replacement API, and the source announcement. Email and Slack alerts at 90, 30 and 7 days before each relevant sunset. A clean nothing affects you state is a feature, show it proudly.

Pages: landing, dashboard, deprecation detail, repo settings, admin review queue.

Pricing: 29 dollars a month for 5 repos, 99 for 25 repos and Slack alerts.