Found by the #126 research sweep, in released code — v1.16.1 and earlier are affected.
Amazon Bedrock publishes an input_images price dimension for the cohere.embed-*-v3 models. The gateway has never recorded that quantity, so an image embedding on a v3 model is attributed at $0: the call bills the operator's AWS account and the gateway's usage and cost reporting show nothing for it.
cohere.embed-v4:0 is not affected — it publishes only input_tokens, and an image's tokens already arrive inside x-amzn-bedrock-input-token-count (measured 27 vs 1 for a text-only call), so the v4 path is honest as it stands.
Filed separately from #126 rather than folded into it: the fix predates that feature, so release notes and git bisect both want it as its own fix: commit.
Ref: .claude/skills/stdapi-usage-pricing (Dimension / UsageKey model, price resolution)
Found by the #126 research sweep, in released code — v1.16.1 and earlier are affected.
Amazon Bedrock publishes an
input_imagesprice dimension for thecohere.embed-*-v3models. The gateway has never recorded that quantity, so an image embedding on a v3 model is attributed at $0: the call bills the operator's AWS account and the gateway's usage and cost reporting show nothing for it.cohere.embed-v4:0is not affected — it publishes onlyinput_tokens, and an image's tokens already arrive insidex-amzn-bedrock-input-token-count(measured 27 vs 1 for a text-only call), so the v4 path is honest as it stands.Filed separately from #126 rather than folded into it: the fix predates that feature, so release notes and
git bisectboth want it as its ownfix:commit.Ref:
.claude/skills/stdapi-usage-pricing(Dimension / UsageKey model, price resolution)