{"version":"2.1.239","anchor":"cost-figures-apply-a-1-1x-factor-for-us-region-inference","canonical_anchor":"cost-figures-apply-a-1-1x-factor-for-us-region-inference","heading":"Cost figures apply a 1.1x factor for US-region inference","tier":"notice","area":"Cost Reporting","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/cost-figures-apply-a-1-1x-factor-for-us-region-inference","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Cost figures apply a 1.1x factor for US-region inference\n\nCost figures multiply by 1.1 for US-region requests, so reported spend rises.\n\n**What**\n\nReported 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.\n\n**Details**\n\n- The region comes from an `inference_geo` field on the API response, so this is decided by the server, not by any client setting or flag.\n- The field is carried through the helper that normalises usage records and defaults to an empty string when absent, which yields the 1x factor.\n\n**Evidence**\n\n`inference_geo`\n\n- Area: Cost Reporting\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}