Skip to content

fix(codex): price Flex tier turns and the gpt-reserve / gpt-5.3-spark ids - #1642

Merged
iamtoruk merged 2 commits into
mainfrom
fix/codex-aliases-flex
Oct 5, 2026
Merged

iamtoruk merged 2 commits into
mainfrom
fix/codex-aliases-flex

Conversation

@iamtoruk

@iamtoruk iamtoruk commented Oct 5, 2026

Copy link
Copy Markdown
Member

Two Codex pricing gaps.

Flex tier. service_tier: "flex" was priced at the standard rate. It now uses LiteLLM's *_flex rates per bucket (exact rates, not a multiplier: gpt-5.4 cached input is $0.13/M, not half of $0.25), including the above-272k tier. A model without flex rates stays at standard. The bundled snapshot gains an optional 7th slot on the 125 rows that publish flex rates; standard rates are byte-identical.

Unpriced ids.

  • gpt-reserve (Luna Reserve) now prices as gpt-5.6-luna with its own label. The backend picks the real model and rollouts don't record it, so the cost is marked estimated (GPT-6 Luna, half the price, became the client fallback on 22 Sep).
  • gpt-5.3-spark maps to gpt-5.3-codex-spark.

Both showed $0 with an unknown-model warning before.

Caches: codex v21, codex parse suffix, daily v55, pricing cache schema v7. No PENDING_REDERIVE: call counts don't change.

Checked: lifetime audit on real history is identical to the cent (no flex or reserve calls in it). A synthetic flex/priority/default/long-context fixture matches hand-computed costs; priority and default are unchanged vs main; cold parse equals warm cache.

… ids

Flex turns (service_tier "flex") billed at standard rates. They now bill at
the model's published `<rate>_flex` rates, carried as an optional seventh
snapshot slot (only the flex fields were added to the bundled snapshot). A
model without flex rates still bills Flex at standard.

gpt-reserve (Luna Reserve) prices as GPT-5.6 Luna and gpt-5.3-spark as
GPT-5.3 Codex Spark; both showed $0 with an unknown-model warning.
@iamtoruk
iamtoruk merged commit 3afcbd9 into main Oct 5, 2026
25 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant