EXAMPLE · YOURCOMPANY.COM
- STEP 01
Paste your domain.
That is the whole setup. No agent to install, no code to share. Auterim starts from what your website already shows.
https://yourcompany.comAnalyze - STEP 02
Confirm what you run on.
Auterim lists what it found and how sure it is. You confirm what is right, and add what a scan cannot see, like an AI provider called from your backend.
yourcompany.com5 confirmedVercel · HostingHIGHStripe · PaymentsHIGHSupabase · DatabaseMEDIUMResend · EmailMEDIUMOpenAI · AIADDED BY YOUCloudflare · CDN (not confirmed)POSSIBLEAdd a dependency - STEP 03
Auterim starts watching.
Each provider is tied to the pages it publishes about itself. Those pages are checked continuously. Nothing else is needed from you.
OpenAIWATCHINGChangelogplatform.openai.com/docs/changelog2m agoDocsplatform.openai.com/docs/api-reference4m agoPricingdevelopers.openai.com/api/docs/pricing6m agoDeprecationsplatform.openai.com/docs/deprecations9m agoPoliciesopenai.com/policies12m ago4 more providers · 19 sources - STEP 04
A provider changes something.
Weeks later, OpenAI updates its deprecations page. Auterim captures exactly what moved, word for word, and when.
OpenAI · Deprecations5 Oct · 14:02 UTCShutdown Model ReplacementRemoved: TBD gpt-4o-2024-05-13 TBDAdded: 2026-11-04 gpt-4o-2024-05-13 gpt-4.1 - STEP 05
Noise is filtered.
That same week, your providers published 148 changes. Most were redesigns, blog posts and copy edits. Two changed something that could affect you.
148READ146FILTERED2NEED YOUgpt-4o-2024-05-13 shutdown scheduledMATERIALWebhook retry window shortenedMATERIAL - STEP 06
It is matched to you.
You marked OpenAI as critical and named the model you use. Auterim lines the change up against that, and is plain about what it does not know.
gpt-4o-2024-05-13 shutdown scheduled- CRITICALITY
- Critical, marked by you
- MATCH
- MODEL IN USE
- gpt-4o-2024-05-13
- MATCH
- REPLACEMENT
- gpt-4.1, per OpenAI
- FROM SOURCE
- MONTHLY VOLUME
- Not provided
- UNKNOWN
Deadline · 4 Nov 202630 DAYS - STEP 07
Your code is checked.
PROWith GitHub connected read-only, Auterim searches your selected repositories for the model name. It finds it, and points to the exact place.
VERIFIEDyourcompany/api · src/lib/llm.tsreturn client.chat.completions.create({model: 'gpt-4o-2024-05-13',messages: input, - STEP 08
The fix is prepared for review.
Auterim drafts the change the provider’s own notice recommends. On Business, it opens as a draft pull request on its own branch. Auterim never merges or deploys.
src/lib/llm.tsFOR REVIEWRemoved: model: 'gpt-4o-2024-05-13',Added: model: 'gpt-4.1',messages: input,BUSINESSDraft pull request #214auterim/replace-gpt-4o-2024-05-13 → main - STEP 09
The right people hear about it.
One message in the channel you chose. One issue in the team that owns it, with the evidence and the deadline attached.
#eng-alertsAuterim 14:10OpenAI shuts down gpt-4o-2024-05-13 on 4 Nov. Found in yourcompany/api. A fix is ready for review.ENG-128Replace gpt-4o-2024-05-13 before 4 Nov- DUE
- 3 Nov 2026
- PR
- #214 · draft
- STEP 10
It is on the record.
Your engineer reviews and merges the pull request on Thursday. Every step stays in your history, with its source, ready when someone asks.
Protection historyRESOLVED- Pull request #214 merged by your team9 Oct · 11:24
- Linear issue ENG-128 created5 Oct · 14:10
- Draft pull request #214 opened5 Oct · 14:09
- Verified in yourcompany/api5 Oct · 14:06
- Matched: critical, model in use5 Oct · 14:03
- Change detected · OpenAI Deprecations5 Oct · 14:02
- Watching started · 5 providers14 Aug
You make the decisions. Auterim does the watching.
YOU
- Confirm your dependenciesONCE
- Add context for critical onesONCE
- Review and merge fixesWHEN ASKED
AUTERIM
- Watch providers’ own sourcesALWAYS
- Filter out noiseALWAYS
- Match changes to your contextALWAYS
- Verify in your codePRO
- Prepare fixes for reviewPRO
Start with your domain.
See what Auterim finds, confirm it, and let it watch from there.