Stale pricing for gpt-5.6-sol / gpt-5.6 / daybreak-blue-latest (OpenAI)

Open Beginner friendly
#1,150 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api

Research direction

Locate the catalog entries for gpt-5.6-sol, gpt-5.6, and daybreak-blue-latest described in the issue, then compare their pricing metadata with the supplied OpenAI values. Update the three input, output, and cached-input rates while leaving the unspecified cache-write rate unchanged, and verify that the parent and fallback relationships remain intact.

Written by the indexing model from the issue text.

Description

model-catalog

What changed

OpenAI reduced first-party pricing for the GPT-5.6 Sol family. The catalog still carries the old rates.

Field Catalog (stale) Official (current)
input_cost_per_mil_tokens 5.00 4.00
output_cost_per_mil_tokens 30.00 20.00
input_cache_read_cost_per_mil_tokens 0.50 0.40

All three catalog entries — gpt-5.6-sol, gpt-5.6, and daybreak-blue-latest — carry identical stale values (gpt-5.6 has parent: "gpt-5.6-sol"; daybreak-blue-latest has fallback_models: ["openai.gpt-daybreak-blue-5.6-sol"]).

Note: input_cache_write_cost_per_mil_tokens (currently 6.25) is not listed on the OpenAI pricing page; left unchanged in the spec below. It may also need updating if OpenAI publishes a cache-write figure.

Sources

  1. OpenAI Pricinghttps://developers.openai.com/api/docs/pricing — GPT-5.6 section lists $4.00 input / $20.00 output / $0.40 cached input
  2. OpenAI Model Comparehttps://developers.openai.com/api/docs/models/compare — confirms gpt-5.6-sol at $4.00 / $20.00
Dominant language
TypeScript
Stars
410
Forks
65
Avg merge
18h 29m
Merged PRs (30d)
51

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from braintrustdata/braintrust-proxy

All issues in braintrustdata/braintrust-proxy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.