Geo Control

The global endpoint and the regional ones

The base URL used throughout these docs, https://api.valarhq.ai/v1, is the global endpoint: DNS geo-steering resolves it to the nearest Valar region automatically, so a client in Frankfurt enters through the EU edge and a client in Chicago through the US edge, with failover between regions if one is unhealthy. If you want to be explicit about which region your traffic enters through — a fixed egress path for firewall rules, reproducible latency, or simply no dependence on where your resolver sits — point at a regional endpoint directly:

Endpoint	Region
`https://us.api.valarhq.ai/v1`	United States
`https://eu.api.valarhq.ai/v1`	European Union (Ireland)

Everything else stays identical: use exactly the same API keys and model slugs from the dashboard, the same request shapes, and the same API surface. The base URL is the only thing that changes.

Configure it

import os
from openai import OpenAI

client = OpenAI(
    base_url="https://eu.api.valarhq.ai/v1",  # or https://us.api.valarhq.ai/v1
    api_key=os.environ["VALAR_API_KEY"],
)

import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://eu.api.valarhq.ai/v1", // or https://us.api.valarhq.ai/v1
  apiKey: process.env.VALAR_API_KEY,
});

curl https://eu.api.valarhq.ai/v1/responses \
  -H "Authorization: Bearer $VALAR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "zai-org/GLM-5.2",
    "input": "Hello from the EU edge."
  }'

No key or workspace changes are needed to switch endpoints — the same key works against the global endpoint and both regional ones, and usage from all three lands in the same reporting.

Getting started

Build agents

Run in production

ValarCode

Platform

The global endpoint and the regional ones

Configure it

​The global endpoint and the regional ones

​Configure it

The global endpoint and the regional ones

Configure it