Is databricks-claude-opus-4-5 deprecated?

Q: Is databricks-claude-opus-4-5 deprecated?

No — still supported. Listed by litellm. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

NOT DEPRECATED

Listed by litellm. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

state=alive sunset=none days_remaining=n/a severity=low sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-16 03:02Z

databricks/databricks-claude-opus-4-5

Vendor: databricks. Tracked by 1 of 5 sources.

What each source reports

**endpoint** = the provider's own machine-readable API, the strongest evidence. **provider docs** = the provider's own documentation, read by a model — first-party content, inferred reading. Unlabelled rows are third-party catalogs. Where sources disagree both values are shown rather than silently reconciled.
Source	ID	Context	Max out	In $/Mtok	Out $/Mtok	Sunset
litellm	databricks/databricks-claude-opus-4-5	200,000	64,000	$5.00003	$25	—

Change history

Severity	Change	What	Detected
low	modified	databricks/databricks-claude-opus-4-5: capabilities gained anthropic_thinking_payload	2026-09-13
low	modified	databricks/databricks-claude-opus-4-5: capabilities gained prompt_caching	2026-08-26
info	repriced	databricks/databricks-claude-opus-4-5: cache_read_price_per_mtok n/a to $0.50/Mtok	2026-08-26
info	modified	[source artifact — 9 providers changed identically on the same day] databricks/databricks-claude-opus-4-5: capabilities lost minimal_reasoning_effort; gained output_config	2026-05-29