GPT-5.4 Cyber: Never Priced, Now Removed

The mistake

Trying to price, or call, gpt-5.4-cyber. It used to appear in the full model list behind OpenAI's pricing page, which made it look like one more selectable model. It was never priced — and at the start of October OpenAI removed it from the API entirely.

Why this happened

Being listed and being priced aren't the same thing. When this site first found the id, it showed up only in the raw list of identifiers the pricing page's source enumerated; every price cell beside it was a dash, and its own model page returned nothing. Both surfaces were checked, and both said the same: nothing published. OpenAI's deprecations page then announced its removal in September, effective at the start of October, with the replacement described as "the most capable cyber model available to you."

Why it matters

Tooling built from a raw model list rather than a curated, priced set is exactly what trips here. A script that included this id either errored or — worse — silently treated a missing price as zero or borrowed another model's rate. Now that the id is gone, any such reference fails outright, which is at least loud.

The fix

Remove gpt-5.4-cyber from model lists, configs and fallbacks. If you were looking at it for security work, the route is OpenAI's Daybreak program: Daybreak Blue gives approved defenders general-purpose models such as GPT-5.6 Sol with safeguards for defensive work, and Daybreak Red gives separately approved access to GPT-5.6 Cyber, which has a published price and a full model page. Both need approval before they can be called. And whatever your tooling enumerates, filter against what is actually published and available to your key, not against what appears in a list.

If something still references it

Search model allowlists, fallback chains and evaluation harnesses as well as configs. Fallbacks are the easy ones to miss: they only run when a primary model has already failed, so a fallback that points at a removed model fails at exactly the moment you were relying on it. Replace the id with a model your key can actually call, or remove the fallback entry entirely.