Skip to main content

Venice

Use this when your team already runs on Venice and you want that vendor family to stay explicit in Loong config instead of disappearing behind a generic compatibility route.

At A Glance

FieldValue
Built-in kindvenice
Provider groupDirect Hosted Providers
Protocol familyopenai_chat_completions
Feature familyopenai_compatible
Auth schemebearer
Credential envsVENICE_API_KEY
Aliasesvenice_compatible
Default base URLhttps://api.venice.ai
Request endpointhttps://api.venice.ai/api/v1/chat/completions
Models endpointhttps://api.venice.ai/api/v1/models

Minimal Config

active_provider = "venice"

[providers.venice]
kind = "venice"
api_key = { env = "VENICE_API_KEY" }
model = "auto"

Verify It

loong doctor
loong list-models
loong ask --message "Say hello and name the active provider."
If list-models is unreliable for this account or region, pin an explicit provider.model or add preferred_models instead of leaving recovery implicit.

Auth And Routing Contract

ContractValue
Auth optionalno
Model probe auth optionalno
Default API key envVENICE_API_KEY
OAuth envnone
Primary request routehttps://api.venice.ai/api/v1/chat/completions
Primary model-catalog routehttps://api.venice.ai/api/v1/models