anomalyco / anomalyco/models.dev
openai/gpt-5.4 limit.input may be using the pricing breakpoint instead of the true max input
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
Problem
providers/openai/models/gpt-5.4.toml currently defines:
[limit]
context = 1_050_000
input = 272_000
output = 128_000
However, the OpenAI docs for GPT-5.4 say the model has a 1.05M context window, and also note:
For models with a 1.05M context window (GPT-5.4 and GPT-5.4 pro), prompts with >272K input tokens are priced at 2x input and 1.5x output for the full session for standard, batch, and flex.
Source: https://developers.openai.com/api/docs/models/gpt-5.4
That wording reads like a pricing threshold, not a hard maximum accepted input size.
Why this matters
Projects consuming models.dev use limit.input as an actual input cap for overflow handling / session compaction. With the current metadata, clients may compact at ~252K input tokens even when the backend can successfully accept much larger requests.
Request
Could you clarify whether 272_000 is intended to be the real max input token limit for openai/gpt-5.4, or whether it is the pricing breakpoint?
If it is only the pricing breakpoint, would it make sense to:
- change
limit.inputto the true accepted max input size, or - remove / relax
limit.inputfor this model, and - represent the >272K pricing behavior separately
If 272_000 is in fact the real hard input limit, could you link the authoritative source for that?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read providers/openai/models/gpt-5.4.toml and compare its limit fields with the linked OpenAI GPT-5.4 documentation. Determine whether 272,000 is a hard input cap or a pricing threshold, then confirm that the metadata and any separate pricing representation reflect the authoritative behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100