{"version":"2.1.224","anchor":"inference-geography-can-be-pinned-on-a-managed-agents-agent","canonical_anchor":"inference-geography-can-be-pinned-on-a-managed-agents-agent","heading":"Inference geography can be pinned on a Managed Agents agent","tier":"notice","area":"Claude API Skill","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/inference-geography-can-be-pinned-on-a-managed-agents-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Inference geography can be pinned on a Managed Agents agent\n\nThe Claude API docs describe pinning inference geography to us or global on an agent's model.\n\n**What**\n\nThe skill docs add `inference_geo`, either `\"us\"` or `\"global\"`, set inside an agent's `model` object rather than at the top level as on the Messages API. It is checked when the agent is saved, when a session is created, and on every turn, and it cannot change for the life of a session.\n\n**Details**\n\n- Unlike `effort`, an `inference_geo` given in a per-session `model` override is applied.\n- Omitting it in an override clears the agent's pin.\n- Every model in a multiagent roster must use the same geography.\n\n**Evidence**\n\n`Pinning inference geography`\n\n- Area: Claude API Skill\n- Names: `inference_geo`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5"}