Engy

Inference locations

Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.

usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.

Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.

Declared countries or regions

Not verified
Qwen3.8-27B and GLM 5.3 Flash are listed as Engy-operated ZDR models, but the reviewed catalog, docs and privacy policy do not disclose their GPU countries or a complete failover-location set.

Can locations change?

Worker location and failover geography are not disclosed in the reviewed sources.

Provider region pinning

No documented per-request country or region pin found in the reviewed API docs.

Pinning through TrustedRouter

Not supported by the current TrustedRouter integration.

Infrastructure declaration

Inference countries undisclosed; no verified country-specific residency commitment.

Evidence

Public docs reviewed; physical inference geography unconfirmed. Reviewed 2026-09-26.

• API documentation
• Privacy and processing path

Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.