See the shutdown coming. See where it lands.
When a provider schedules an API version or AI model for retirement, Auterim reads it on the provider’s own page, pins the date, and points to the lines in your code that still call it.Auterim reads the retirement on the provider’s own page, pins the date, and points to the lines that still call it.
The notice is public. Noticing it is the hard part.
- 01The date lives on a page you don’t read.
Retirements are announced on a deprecations page or in a changelog, often months ahead, between dozens of unrelated entries.
- 02The identifier hides in your code.
A model snapshot or API version string sits in a config file or a helper that nobody has opened since it was written.
- 03Missing it shows up as errors.
After the shutdown date, calls to a retired model or version can start failing. Too often the first sign is a failed request in production.
From the source to a fix you review.
- 01ALL PLANS
The notice is captured at the source.
Auterim watches the provider’s deprecations page, changelog and docs. When the table changes, it keeps the exact excerpt and when it was captured.
OpenAI · Deprecations5 Oct · 14:02 UTCShutdown Model Replacement−TBD gpt-4o-2024-05-13 TBD+2026-11-04 gpt-4o-2024-05-13 gpt-4.1Shutdown Model Replace−TBD gpt-4o-2024-05-13 TBD+2026-11-04 gpt-4o-2024-05-13 gpt-4.1Excerpt from platform.openai.com/docs/deprecations - 02ALL PLANS
It is matched to what you use.
The change is lined up against your confirmed dependencies and the context you gave, like the model you call. Where you haven’t said, it says so instead of guessing.
gpt-4o-2024-05-13 shutdown scheduledCRITICALITYCritical, marked by youMATCHMODEL IN USEgpt-4o-2024-05-13MATCHREPLACEMENTgpt-4.1, per OpenAISOURCEVOLUMENot providedUNKNOWNDeadline · 4 Nov 202630 DAYS - 03PRO
Your code is searched for it.
With GitHub connected read-only, Auterim searches the repositories you selected for the exact model name, and binds each match to a file, a line and a commit.
VERIFIEDyourcompany/api · src/lib/llm.tsline 42 · a3f9c2141 return client.chat.completions.create({42› model: 'gpt-4o-2024-05-13',43 messages: input,41return client.chat.completions.create({42› model: 'gpt-4o-2024-05-13',43 messages: input,1 more finding · src/jobs/summarize.ts:18 - 04PRO
A tested fix waits for review.
Auterim drafts the change the provider’s notice recommends and opens it as a Draft PR on its own branch. Someone on your team reviews and merges it.
src/lib/llm.tsFOR REVIEW42− model: 'gpt-4o-2024-05-13',42+ model: 'gpt-4.1',43 messages: input,42−model: 'gpt-4o-2024-05-13',42+model: 'gpt-4.1',43messages: input,GROUNDED INOpenAI’s deprecation notice names gpt-4.1 as the recommended replacement.Draft PR #214 · Auterim never merges or deploys - 05ALL PLANS
The deadline stays pinned.
Until someone closes it, the date sits in your upcoming deadlines next to its status, and every step is kept in your protection history.
Upcoming4 NOV 2026OpenAI · gpt-4o-2024-05-13 shutdownFIX IN REVIEW1 FEB 2027Supabase · legacy API keys retiredNOT AFFECTED
Evidence first. Then the fix.
Every finding carries its source, or says plainly that evidence is missing. Auterim never merges or deploys.
Pro covers it. Verify it. Fix it.
Pro is the first plan with verified impact in your code and tested fixes. Core still watches, filters and alerts. Your 5-day Pro trial starts when protection goes live.
Compare plans and pricesOther changes Auterim watches for.
Start with your domain.
See what your website runs on, confirm it, and let Auterim watch from there.