Skip to content

DUX-11214: Document unverified cache-write pricing gap for GPT-5.6 Bedrock entries #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
samuelboland merged 1 commit into from
Aug 5, 2026
Merged

DUX-11214: Document unverified cache-write pricing gap for GPT-5.6 Bedrock entries #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions spec/ruby_llm/models_gpt_5_6_bedrock_spec.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,15 @@
RSpec.describe RubyLLM::Models do
include_context 'with configured RubyLLM'

# None of these three hand-added entries (see 7791056d) carry a
# cache_write_input_per_million rate, matching every other OpenAI-family
# model in models.json — no OpenAI model in this registry has that field
# modeled. This is consistent with, but NOT independently verified
# against, OpenAI/Bedrock pricing docs for GPT-5.6 specifically: whether
# Bedrock charges a distinct (non-zero) cache-write rate for these models,
# the way it does for Anthropic's cache_creation_input_per_million, is
# unknown. Revisit if models.dev adds real entries for these ids, or if
# OpenAI/AWS publish a documented cache-write rate for GPT-5.6.
{
'openai.gpt-5.6-sol' => { input: 5.0, output: 30.0, cache_read: 0.5 },
'openai.gpt-5.6-terra' => { input: 2.5, output: 15.0, cache_read: 0.25 },
Expand Down