Skip to main content

Regions Overview

Use this page as the public reference for Verdictan region and locality terms at this time.

Start with the requested region​

The primary region concept is the requested region. It is the region for the active CLI command, gateway workflow, or published endpoint.

Other region-related values can be active at the same time:

  • Profile default region: The CLI stores this region for a named profile in ~/.verdictan/config.yaml.
  • Process-wide override: verdictan --region <region> sets VERDICTAN_REGION for the active CLI process.
  • Published-endpoint locality: The hostname for a Verdictan-managed public endpoint controls locality and publication routing.
  • Resource home region: Some resources or provider targets are available in only one region. A request for a different region can return an empty or unavailable result. It does not return globally aggregated results.

Set a default region for a CLI profile​

The CLI stores profile defaults in ~/.verdictan/config.yaml.

verdictan configure set region eu-west --profile default
verdictan configure get region --profile default
verdictan configure list-profiles

verdictan regions use <region> and verdictan regions switch <region> are aliases. The two commands write the same default region for the profile.

Examine the active region​

Use these commands to examine what the CLI sees and uses:

verdictan regions list
verdictan regions list --json
verdictan regions list --enabled
verdictan regions list --group eu
verdictan regions current
verdictan regions status

verdictan regions current prints this information:

  • It prints the resolved region.
  • It prints the source that won.
  • It prints the resolved API endpoint.
  • It prints if the active scope is global or regional.

Active CLI precedence​

For the active verdictan regions current CLI behavior, the CLI resolves the region in this sequence:

  1. The CLI first uses the process-wide override from verdictan --region <region> or VERDICTAN_REGION.
  2. The CLI uses profiles.<profile>.default_region as the second option in ~/.verdictan/config.yaml.
  3. The CLI uses the legacy root-level default_region field as the third option.

The CLI resolves the API endpoint through a different config chain:

  1. The CLI first uses --api-url.
  2. The CLI uses VERDICTAN_API_URL as the second option.
  3. The CLI uses api_url as the third option in ~/.verdictan/config.yaml.
  4. The CLI uses https://api.verdictan.com as the fourth option.
Declarative-config precedence

~/.verdictan/config.yaml controls the requested region for API-backed CLI commands. policy-config.yaml controls the gateway runtime and provider locality.

A published hostname keeps its own locality binding. The CLI profile default does not change runtime routing.

If these values do not agree, correct the declarative config or hostname.

Region behavior

Verdictan does not use nearby regions or regions in the same family as automatic alternatives. If a workflow must use a specified region, the product stops the operation. It does not change the region without notification.

Console availability​

The active customer console does not give a Settings → Regions page or a browser-session region selector.

Use the CLI commands in Examine the active region to examine a profile region. Use these commands to change the requested region.

For managed public endpoints, select the hostname with a locality that matches the workload. The console does not change that binding.

Managed public endpoints​

A managed public endpoint is a published organization gateway. The hostname you select changes locality and publication routing. It does not change the auth model.

The endpoint dispatches upstream traffic with your own provider credentials. Verdictan does not add a platform provider credential at the public endpoint.

Published traffic familyBehavior
*.ai.global.verdictan.comThis global entrypoint selects an eligible published region after the organization and region rules apply.
*.ai.eu.verdictan.comThis hostname gives an EU locality commitment.
*.ai.us.verdictan.comThis hostname gives a US locality commitment.

The API assigns an immutable 12-character lowercase alphanumeric publication key as the wildcard label. An example hostname is abc123def456.ai.eu.verdictan.com.

Do not use an organization slug or an agent slug as the wildcard label.

Root hosts at verdictan.com, eu.verdictan.com, and us.verdictan.com are status surfaces for discovery only. They do not process customer model traffic.

When an incorrect region looks like a missing resource​

Start with these checks:

  1. Run verdictan regions current.
  2. Make sure that the resolved API endpoint is the specified endpoint.
  3. Make sure that the resource or provider target is available in that region.
  4. If you use a published hostname, make sure that its locality matches the specified workload.

Next steps​