docs: grok-imagine-image-pro still quoted the pre-correction price on two pages - #92
Merged
Merged
Conversation
… two pages The gateway corrected this SKU's 1K size row from $0.07 to the $0.05 it advertises (blockrun#543, live since 2026-09-08). The catalogue moved; these two pages did not, so both kept quoting the old number — 39% and 40% over what a caller is now charged. api-reference/models.md:264 $0.0735 -> $0.0525 api-reference/image-generation.md:59 $0.0745 -> $0.0535 The two figures differ because the two pages use different conventions, and each is internally consistent, so each was moved on its own terms rather than unified: models.md lists margin only (google/nano-banana, same $0.05 catalogue price, is $0.0525 there) and image-generation.md lists margin plus the $0.001 transaction fee ($0.0535 for the same model). Both now agree with nano-banana on their own page, which is the check that matters — same catalogue price, same published number. resources/changelog.md's $0.07 is left alone: it is a dated record of what the price was, not a claim about what it is. Found by the blockrun-sol session reading the published surfaces by hand after porting the fix. The reason no test caught it is being addressed on the gateway side. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GJ6wG4k5TgeUgYneCMz1oc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The gateway corrected this SKU's 1K size row from $0.07 to the $0.05 it
advertises (blockrun#543, live since 2026-09-08). The catalogue moved; these two
pages did not, so both kept quoting the old number — 39% and 40% over what a
caller is now charged.
api-reference/models.md:264 $0.0735 -> $0.0525
api-reference/image-generation.md:59 $0.0745 -> $0.0535
The two figures differ because the two pages use different conventions, and each
is internally consistent, so each was moved on its own terms rather than
unified: models.md lists margin only (google/nano-banana, same $0.05 catalogue
price, is $0.0525 there) and image-generation.md lists margin plus the $0.001
transaction fee ($0.0535 for the same model). Both now agree with nano-banana on
their own page, which is the check that matters — same catalogue price, same
published number.
resources/changelog.md's $0.07 is left alone: it is a dated record of what the
price was, not a claim about what it is.
Found by the blockrun-sol session reading the published surfaces by hand after
porting the fix. The reason no test caught it is being addressed on the gateway
side.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GJ6wG4k5TgeUgYneCMz1oc