Cost figures multiply by 1.1 for US-region requests, so reported spend rises.
What's wrong with this entry?
Reported per-request cost now multiplies the token-derived subtotal by 1.1 when the API says the request was served in the US region, and by 1 otherwise. The web search fee is added afterwards and is not multiplied. Dollar figures in cost and usage reporting will be higher for US-region traffic than in previous builds.
- The region comes from an
inference_geofield on the API response, so this is decided by the server, not by any client setting or flag. - The field is carried through the helper that normalises usage records and defaults to an empty string when absent, which yields the 1x factor.
inference_geo
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Cost summary can note that figures use your organization's rates
Both mention cost
-
v2.1.223
API error metadata is recovered from wrapped errors
Both mention reporting