Repository navigation
fix(cli): price GPT Image 2.6 and every GPT Image reference picture - #7307
Conversation
The media-use image estimate priced every non-default model as GPT Image 2.5 and charged references at $0.0082 after the first. fal bills every reference picture, the first one too, at about $0.0125, and the price book now does the same. GPT Image 2.6 and 2.6-flare take 2.5's prices; nano-banana-2.1 gets its own; any other model is not priced ahead instead of guessed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Verdict: COMMENT (needs fix) · 0 blocker · 1 important · 0 nits
The numbers match image_catalog.py and the hf_image price-book rows on EF master (12.5 per reference, 33.6 + 1.68 for nano-banana-2.1, one round-up). The Comments ratchet is red because of this diff (inline). It isn't a required check, but I'd approve once it's green and Windows render finishes.
Scope
Read the full diff and pricing.ts at the head. Checked against EF image_catalog.py (_GPT_VENDOR_COST, nano-banana-2.1 VendorCostEstimate) and the price book's hf_image rules: -reference-v2 rows for 2.5, plus 2.6/flare output and reference rows. Recomputed the tests' 40/53/240/37 credits and the $0.09 case. No other 0.0082 or reference-pricing site in the repo. CI at this head: Test (cli 1/2, 2/2), Typecheck, Build and Skills manifest are green. Comments is red. Flake gate and Windows render were still running.
— Genesis
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…-com#7336-heygen-com#7358 Adopt heygen-com#7304 (without CLI renderDiagnostic, needs heygen-com#6725), heygen-com#7331, heygen-com#7332, heygen-com#7334, heygen-com#7337, heygen-com#7336, heygen-com#7339, heygen-com#7289, heygen-com#5594, heygen-com#6900, heygen-com#7322, heygen-com#7342, heygen-com#7343, heygen-com#7350 (onProgress only), heygen-com#7352, heygen-com#7348, heygen-com#7344, heygen-com#7353, heygen-com#7356 and heygen-com#7355. Defer heygen-com#5708 (needs heygen-com#6911) and heygen-com#7345 (READ_VERSION 4 vs 7); heygen-com#7307 not applicable. Re-read 14 moved pins, pin 6 new PRs (monitored 126). Make checkReportFile module-private and suppress the cross-package closeTestChrome duplicate for fallow. Co-authored-by: Miguel Ángel <miguel.sierra@heygen.com> Co-authored-by: SophiaHuangCc <129631224+SophiaHuangCc@users.noreply.github.com> Co-authored-by: Dante <duanjl.china@gmail.com> Co-authored-by: Muzzy5150 <muzzy5150yt@gmail.com> Co-authored-by: ump45nose <52391318+ump45nose@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What
media-use generate --type imagenow prices GPT Image 2.6 and 2.6-flare, and counts every reference picture on a GPT Image edit at about $0.0125. Before, it charged $0.0082 a reference after the first. nano-banana-2.1 gets its own price. A model the CLI doesn't know is reported as "not priced ahead" instead of being priced as GPT Image 2.5. The media-use skill's price table matches.Why
gpt-image-2.6andgpt-image-2.6-flareto/v3/imagesat 2.5's prices. 2.6 bills the same tokens as 2.5.nano-banana-2was priced as 2.5. Sonano-banana-2.1(33.6 credits plus 1.68 a reference) was quoted at GPT rates, and--max-creditschecked against the wrong number.Example: a 16:9 GPT Image edit with one reference was quoted at 40 credits, the same as no reference. The price book now charges 53.
Related work
How
pricing.ts: explicit image models. GPT Image is the per-aspect output price plus $0.0125 times the number of references. nano-banana-2.1 is $0.0336 plus $0.00168 a reference. An unknown model returns null, so--max-creditsrefuses it rather than guessing.--modelhelp andheygen.md: list the five image models.Test plan
src/heygen/generate.test.tspasses, 55 tests.tsc(no errors in touched files), fallow,lint-skills,check-skill-mirrorandcheck:studio-copy-dashespass.skills/media-use/references/heygen.md.— Rames
🤖 Generated with Claude Code