MISAK SYSTEMS

T-01For teams that ship integrationsEarly access

Find the deprecated APIs your code actually uses, before they break.

API Sunset Autopilot scans your repository for API versions, SDK pins and AI model IDs that vendors have scheduled for shutdown, matches every hit to the vendor's official date, and tells you exactly which file and line will fail. Optional: a ready-to-review migration patch.

HU · Megtalálja a kódodban azokat a kivezetés alatt álló API-verziókat, SDK-kat és AI-modellazonosítókat, amelyek hamarosan leállnak.

Spec
Google Ads API v22Sunset 7 Oct 2026
Shopify Admin API 2025-10Accessible until 16 Oct 2026
OpenAI legacy model snapshotsShutdown 23 Oct 2026
Anthropic claude-sonnet-4-5-20250929Retirement 30 Nov 2026
Google Ads API v23Sunset February 2027 (tentative)

1Problem

Deprecations rarely fail loudly in advance

  • 1.1Vendor sunset notices go to an inbox nobody reads, while the code that depends on them was written by someone who has left.
  • 1.2SDKs pick their default API version silently: an old pin in requirements.txt or package.json can keep you on a version that is about to stop working.
  • 1.3AI model IDs are plain strings scattered across code, config and environment files. Retired IDs turn into hard errors on the shutdown date.
  • 1.4Some platforms do not reject old versions but silently move you to a newer one, so behaviour changes without an outage to warn you.

2How it works

  1. IN

    repository

    public URL or read-only access

  2. 01

    finder

    manifests, SDK pins, model IDs

  3. 02

    rule match

    verified vendor dates

  4. OUT

    report

    file, line, deadline, source

  5. OPT

    patch

    reviewable PR (paid)

Fig. 1 — API Sunset Autopilot pipeline
  1. 2.1

    Point it at a repo

    Send a public repository URL, or grant read-only access to a private one. Nothing is pushed to your code.

  2. 2.2

    Scan against verified rules

    Each rule is tied to the vendor's official deprecation page and date. Hits are reported per file and line, with the SDK version or model ID found.

  3. 2.3

    Get the report, then decide

    The free report shows what will break and when. If you want it fixed, order the migration patch for that repository.

apisunset scan ./your-repoExample output · illustrative data
$ apisunset scan ./your-reporules loaded: 4 (last verified 2026-10-04) [HIGH] google-ads-v22       requirements.txt:12   google-ads==28.2.0  -> implicit API v22, sunset 2026-10-07[HIGH] openai-legacy-2026   app/llm.py:41         model="gpt-4-turbo"  -> shutdown 2026-10-23[INFO] shopify-2025-10      config/shopify.yml:3  api_version: 2025-10 -> falls forward after 2026-10-16 3 findings · 2 high · report: out/reports/your-repo.md

3Deliverables

3.1

Repo scan report

Every affected file and line, the rule it matched, the official deadline and a link to the vendor's migration guide.

3.2

Dependency pin check

SDK versions that imply a deprecated API version by default, with the minimum safe version per library.

3.3

Migration patch (paid)

A reviewable patch or pull request: version bumps and the mechanical code changes, with notes on what needs a human decision.

3.4

Model ID swaps flagged, not guessed

A retired AI model is replaced by one that behaves and costs differently, so these are listed with options for you to choose.

3.5

Sources you can check

No unverified deadlines. Each date in the report links to the vendor's own page and the date it was checked.

3.6

Monitoring (coming soon)

Re-scan on new deprecation notices and on your new commits, so the next sunset does not surprise you.

4Pricing

Free repo scan

€0

One repository, current rule set.

  • Findings by file and line
  • Official deadline per finding
  • Migration guide links

Migration patch

from €59 / repo

The fix, ready for your review.

  • Patch or pull request for the findings
  • Dependency version bumps
  • Notes on behaviour changes to test

Early access. Larger or multi-service repos are quoted before any work starts.

Monitoring

Coming soon

Ongoing watch for new sunsets.

  • Rule updates from vendor notices
  • Re-scan on change
  • Alert by email

Early access prices, excl. any applicable VAT. No payment is taken on this site.

5FAQ

Which APIs are covered today?

The current rule set covers Google Ads API version sunsets (including client library pins), Shopify Admin API version retirement, retired OpenAI model snapshots and the retirement of an Anthropic Claude model snapshot. New rules are added only after the deadline is verified on the vendor's own page.

Do you need write access to my repository?

No. The scan only reads code. For private repositories, read-only access or a temporary export is enough. The migration patch is delivered as a patch file or a pull request that you review and merge yourself.

Is my code stored or used for anything else?

Your code is used only to produce your report and patch, and is deleted after delivery unless you ask us to keep it for monitoring.

What if the scan finds nothing?

Then you get a short report saying which rules were checked against which files, so you know it was actually looked at.

Can you guarantee nothing will break?

No tool can. The report covers the rules listed in it. The patch is meant to be reviewed and tested in your pipeline before release.

6Official sources

Dates were read from these official pages on 4 October 2026. Vendors can change dates; the report always shows the date each rule was last checked.

7Request

Request the free scan

Tell me where to look. You get the free result first and decide afterwards whether the paid deliverable is worth it.

Built and run by Misak Systems (Ottó Misák, software engineer) · Hungary, EU

Privacy: we only use your name, email and URL to reply and run the requested scan. No newsletter, no reselling, no tracking pixels. Private repositories are only accessed with access you explicitly grant.