Skip to main content
Use headless mode when the gateway must load configuration from local files instead of synchronizing with Edgee. It still needs a valid license and network access to the configured model providers. A fully isolated deployment needs reachable provider endpoints inside that environment.

​
Required inputs

Use the deployment credentials and configuration supplied for your licensed organization. A made-up bearer string does not become a valid Gateway token by adding it to TOML.

​
Gateway file structure

This is an illustration of the structure, not a ready-to-run configuration. Replace the key lookup value, identifiers, models, and pricing with those for your deployment. The API-key table name corresponds to the token’s k claim, not the entire bearer token.
Costs are nanodollars per token: 1 USD is 1,000,000,000 nanodollars. The sample cost fields illustrate units, not current provider pricing. expires_at uses Unix seconds; choose your intended expiry.
Headless mode does not synchronize usage from Edgee. Without that usage data, usage-based limit checks fail open. Do not use the sample max_usage field as proof of an enforced spending cap. Connected mode supplies current usage through synchronization.

​
Provider credentials

The provider credential file is flat TOML, without a section header:
Mount it read-only and set PROVIDER_KEYS_FILE to its container path. In connected mode this file is ignored; credentials come from configuration sync instead. Keep both deployment and provider credentials out of version control.

​
Verify a real request

A successful /status health response only proves the server is running. Test authentication, model configuration, and provider access too:
Expect a successful model response. For an authentication error, check the token and configured key. For a provider error, check provider credentials and connectivity. Inspect gateway logs without printing secrets. To point an agent at this deployment, follow CLI gateway configuration. For connected mode, confirm the request also appears in the expected organization’s usage records.