Providers, models and APIs

A model retirement never shows up as a new package version. Your code keeps sending gpt-4.1-nano until the day the provider stops answering. Teire reads the providers' own deprecation pages and changelogs and finds the model IDs and endpoints in your code. Then it fixes them like any other change.

Readers written for these providersCopy Anchor Link

These readers parse each page's own tables and headings in code, with nothing inferred. A provider counts as used when one of its SDKs is installed, in any of the six ecosystems, or its API host appears in a URL in your code. Its pages are read then, at most once every 6 hours, shared by every repository. Nothing is read on a schedule.

Any other providerCopy Anchor Link

When your code calls an API host that has no reader, Teire discovers the provider. It finds hosts in two ways:

1. a URL in your code whose host or path looks like an API (api., /v1, /api),
2. an installed SDK whose published code names an API host on its own domain: the npm tarball, the PyPI wheel, the Go module zip, the .crate, the .gem or the Maven -sources.jar of the exact version you lock. Up to 40 SDKs are read per scan, as text, never run.

Then it looks for the provider's notices:

1. llms.txt on the docs host and the domain, scoring links that say deprecat, retire, sunset or changelog,
2. if that finds no deprecations page, a Tavily search limited to the provider's own domains,
3. last, /docs/deprecations and /deprecations on its busiest docs hosts.

At most 3 pages are kept per provider, deprecations first. Every fetch and redirect must stay on the provider's domains.

The quote gateCopy Anchor Link

A page read by Nemotron becomes one record per model or endpoint, each with a verbatim quote of up to 400 characters. Code then checks every record before Teire acts on it:

1. The quote is found in the page Teire fetched.
2. The model ID is inside its own quote. A replacement missing from the quote is removed.
3. Every source is on the provider's official domains.
4. For a page Nemotron read, the ID, the replacement and the date all appear in the quotes.

An item whose quote is not in the page, or whose ID is not in its quote, is dropped. A record that fails the final checks is kept as unconfirmed and never applied to code on its own. Where your code passes its ID as a model, the scan says check by hand in a needs-a-human issue, naming why the record couldn't be confirmed. Comment @teire fix to try it anyway: the run uses the record and opens a draft labelled unconfirmed, with a warning at the top, whatever the checks say. The same rule applies to package release notes: an item that doesn't quote the fetched text is dropped.

Finding the models in your codeCopy Anchor Link

ast-grep searches the strings of your JS/TS, Python, Go, Rust, Ruby, Java and Kotlin code for the exact IDs the confirmed records name. It also searches config files (.env*, YAML, TOML, JSON, INI, .properties) for them as whole words. Where an ID sits decides the verdict:

Nemotron then traces the inconclusive ones. It is shown the files holding the IDs and the JS/TS or Python files that import them, and asked whether each ID reaches a request. Its answer counts only if the line it cites exists in a file it was shown and names a model. Test and fixture files are never fix sites.

If your code builds the provider's client from an environment variable such as OPENAI_BASE_URL, the deployment decides which service answers. Teire marks those findings inconclusive instead of affected.

Endpoints work the same way: a URL in your code on the provider's host whose path is the removed one, or below it.

API changes from OpenAPI specsCopy Anchor Link

For API hosts your code calls by URL, Teire looks for the provider's OpenAPI spec. It searches the GitHub organisation behind the provider's SDK, or uses a specUrl you set in teire.yml. It diffs the spec with oasdiff 1.34.1 from your position, which is the API version pinned in your code (apiVersion, stripe_version…) or else the date of your last commit touching those files. Breaking changes on operations your URLs reach become findings.

The fixCopy Anchor Link

One PR per provider. Each retired model is swapped for the replacement the provider names. If that replacement was later retired too, Teire follows it, up to 5 hops. When a provider names several options, the agent chooses. Parameter changes from the same provider ride along as migration notes when your code uses that parameter. Then your checks run before and after, as for packages. For a model that has already stopped working, the baseline's checks fail by definition. "Already failing" is not accepted there: the run keeps going until the checks pass after the change.

The public catalogCopy Anchor Link

Everything Teire has read for the repositories it scans is public, and every page links to the others:

A change only appears once a scanned repository depends on it. The same records are available as JSON from /api/catalog/changes, which the CLI reads.