Check your exposure

Which models are you running, and when do they retire?

Paste the model ids out of your configuration. You get each one's published retirement date with a link to the page it was read from, the days remaining, and which of them are aliases the provider can repoint without telling you.

The dates are the providers' own, read from their published deprecation pages on . This is a calendar with a parser in front of it: it tells you when you will have to do the work, not whether the work will succeed.

.env, YAML, JSON, a requirements manifest - parsed in your browser, never uploaded.

This runs entirely in your browser. The model ids, and any file you drop, are matched against a copy of the feed already on this page - nothing is uploaded and nothing is stored.

Or read every retirement we track, grouped by the date it takes effect.