Claude US-Only Inference: The 1.1× Regional Billing Multiplier

What the residency option actually changes

Anthropic documents inference_geo set to us for Claude 4.6 and later, applying a 1.1× multiplier to first-party token billing categories. Input, output, cache writes and cache reads are affected; global inference uses the unmodified list rate. The supported parameter is model-specific. Do not send it to older endpoints that do not support the feature or assume it creates end-to-end storage residency assurances beyond the documentation.

The multiplication belongs after the category calculation

If a hypothetical eligible job incurs $8 in output charges, $3 in input charges and $1 in eligible cache activity, US-only inference produces ($8+$3+$1)×1.1 = $13.20 before taxes. Applying the factor only to output underestimates the invoice. A separate factor might apply to some batch paths, depending on the contract; preserve a clear modifier order, billable category list and billed geography rather than storing an unexplained flat blended token price.

Cloud-provider regions have their own rules

The same pricing reference distinguishes Claude Platform first-party routing from partner-operated Amazon Bedrock and Google Cloud endpoints. Their regional or multi-region endpoint prices are set by those providers; the first-party 1.1× factor should not simply be copied into a Bedrock or Vertex AI row. Enterprise contracts may also contain data boundary conditions and private offers that the general list-price page cannot disclose. Procurement should validate a residency policy and commercial quote together.

Compliance caveat for global customers

Using a US inference route says something about the relevant model execution location; it does not alone determine application logging, payment geography, backups, analytics or what a customer may lawfully transfer across borders. The pricing article cannot certify GDPR compliance or any particular contractual guarantee. Identify whether your organisation requires geographic processing, contractual data residency, data retention, or all three, and obtain the current supplier terms before enabling production data flows.

Before choosing a paid tier

Obtain the billing quote for the exact Anthropic product, account geography, tier, model or subscription, currency and commitment length. If the provider offers several kinds of meters, forecast each independently rather than summing quantities in incompatible units. The relevant captured meters here include dimensionless_rate_multiplier. Build a low, expected and high workload from your own request logs or editorial schedule; a pricing page is not a credible estimate of how many retries or approvals your team will need.

For governance, add an approval threshold for paid overages, reconcile invoices with metered activity, and schedule a quarterly or release-triggered source audit. The absence of an identified enterprise rate, promotional expiry or regional tax line is not evidence that the amount is zero. This guide does not represent a product trial, capability benchmark, procurement offer or warranty of uninterrupted access.

Historical availability and boundaries

Preserve the precise source version, checked date and any stated effective date before reusing these figures. A model launch announcement may confirm an introductory token rate without proving which private offers remain available; a mutable plan page can describe a later product state. If a source changes after this cutoff, publish a new snapshot instead of silently editing the historical record. Specialised product evaluations belong to the relevant AI 02–09 editorial teams, while this article documents the billing model and its limitations.