chore: update model catalog from bot issues - #1063
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Codex (@codex) review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fe784f1625
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| "input_cost_per_mil_tokens": 2.2, | ||
| "output_cost_per_mil_tokens": 13.2, | ||
| "input_cache_read_cost_per_mil_tokens": 0.22, | ||
| "input_cache_write_cost_per_mil_tokens": 2.75, |
There was a problem hiding this comment.
Use Bedrock's in-region GPT-5.6 prices
For this Bedrock model ID (and the Luna block just below), these are the discounted/global-looking rates, but AWS documents openai.gpt-5.6-terra/openai.gpt-5.6-luna as bedrock-mantle in-region model IDs with no Geo or Global inference IDs, and the Amazon Bedrock pricing page still lists the in-region rates as Terra $2.75/$3.44/$0.28/$16.50 and Luna $1.10/$1.38/$0.11/$6.60. With the lower values here, any catalog-based Bedrock cost estimate for these IDs underreports actual in-region usage. Sources: https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-56-terra.html and https://aws.amazon.com/bedrock/pricing/
Useful? React with 👍 / 👎.
Automated daily batch of model catalog updates from bot issues.
Included issues
Summary
openai.gpt-5.6-terraopenai.gpt-5.6-lunaopenai.gpt-5.6-terraopenai.gpt-5.6-luna2
3
Verified metadata
#1061: [BOT ISSUE] Bedrock: fix incorrect pricing for openai.gpt-5.6-terra and openai.gpt-5.6-luna
Verification notes
Verification
sync_models vs proposed update
sync_models cross-check found differences. Official provider verification was used for the applied values, and sync_models discrepancies are listed below for review.