benchrEvidence boundary
Lifecycle status, dates, IDs, official replacements, and old/new prices come from deprecations.json. An item labelled “benchr editorial alternative” is judgment, not provider guidance.
Turn a deprecated model ID into a migration plan.
Paste one model ID, a model name, or a configuration excerpt. The assistant finds exact lifecycle matches, keeps official guidance separate from benchr judgment, and gives you a checklist—not a false promise of a drop-in replacement.
What are you migrating?
Exact API IDs produce the safest match. A configuration excerpt can reveal more than one retiring dependency.
Lifecycle matches and next steps
Status, dates, replacements, and prices are rendered directly from the current benchr lifecycle record.
Your analysis will appear here. Try a retired snapshot ID, a legacy model name, or a configuration excerpt.
Loading…
Safe rewrite boundary
The assistant proposes text only when one old API ID matches and the official record supplies one unambiguous replacement ID. It changes the identifier—not the surrounding SDK or application contract.
Production boundary
Provider dates may differ across direct APIs, cloud marketplaces, regions, or account tiers. Confirm the linked source, test representative workloads, canary traffic, and keep a rollback path.
Frequently asked questions
Does benchr upload or store my configuration?
No. The assistant downloads benchr's public model and deprecation data, then analyzes your text inside the browser. It does not upload, save, or share the pasted configuration.
Does no match mean my model is safe from retirement?
No. No match means only that the current benchr record did not match the text. Provider availability can vary by platform, region, and account, and a provider may change its lifecycle documentation. Check the linked official source.
Is the suggested configuration a drop-in migration?
No. The assistant changes only one exact model identifier when the record contains one unambiguous official replacement ID. You still need to review SDK parameters, context limits, tools, output formats, safety behavior, and application tests.
How is the migration price difference calculated?
It compares the retiring and replacement input and output prices recorded in deprecations.json, per million tokens. If either price pair is incomplete, the assistant reports that the comparison is unavailable instead of assuming zero.