Skip to main content
For hosted Sudoiq, you typically only need an API key from Settings and the default base URL. Self-hosted variables apply when you run your own API stack (see Docker).

​
Python client (suggested names)

VariableRequiredDefaultNotes
ASAPI_API_KEYYes*—API key (sk_...) for AsapiClient.set_api_key.
ASAPI_BASE_URLNohttps://sudoiq.com (typical)Execution API origin; override for self-host.
*For server-side calls.

​
agentservice CLI

VariableRequiredDefaultNotes
AGENTSERVICE_API_KEYYes*—Same as key from Sudoiq settings; also set via agentservice login.
Config file locations: ~/.config/agentservice/config or ~/.agentservice (api_key=, host=). See CLI.

​
PDF demo (typical variables)

VariableRequiredDefaultNotes
SUDOIQ_KEYYes—API key read by the demo factory.
SUDOIQ_URLNohttps://sudoiq.comBase URL for the client.
AGENT_IDNo—Overrides agent id file from one-time upload.
SUDOIQ_DEMO_MAX_WAITNo3600Demo-specific upper bound while waiting for a chat run.
Check the demo’s .env.example for the authoritative list.

​
Self-hosted Docker

Compose stacks usually inject API keys, database URLs, Redis, and signing secrets via .env next to docker-compose.yml. Names are repository-specific — copy the template from your backend repo when you follow Docker.

​
SDK timeouts

Interactive streaming runs use a default response timeout (wall-clock seconds) in the asapi package (DEFAULT_INTERACTIVE_RUN_RESPONSE_TIMEOUT, often one hour). Override per call with response_timeout= on execute_agent / run_agent, or pass float("inf") where supported. See Timeouts and errors.