Region pinning

Pin a request to a geographic region and Sable routes it to a node there — or refuses. It never silently sends your data somewhere else. This is what makes the sovereign tier's jurisdiction promise concrete rather than aspirational.

Pinning a request

/v1/chat/completions and /v1/embeddings accept an optional sable_region body field. Pass a broad region (eu, us, ap) or a full code (eu-central, eu-west, us-east, ap-southeast).

resp = client.chat.completions.create(
  model="sable-deepseek-v3",
  messages=[{"role":"user","content":"Summarize this filing"}],
  extra_body={"sable_region": "eu"},
)

No silent fallback

If no node serves the requested region, the request fails with 400 — it is never quietly routed elsewhere. That refusal is the guarantee: a request pinned to eu either runs in the EU or doesn't run at all.

{
  "error": {
    "type": "bad_request",
    "message": "no Sable node serves region 'eu'"
  }
}

Confirming where it ran

The region a request actually executed in comes back two ways:

• x-sable-region response header
• the region field inside the signed receipt

Because the region is part of the signed payload, the location is tamper-evident: the same secp256k1 signature that proves the inference happened also proves where. That's the mechanism behind sovereign-tier jurisdiction pinning — see Privacy tiers.