Onlist sends each request to one of these providers. Smart, the default, favors reliability first, then effective price and speed; the higher a provider sits here, the more of the traffic it gets.
| Provider | Chat | ||||
|---|---|---|---|---|---|
| $0.05 | $0.15 | Hit rate— Cache read$0.005 | — |
Capabilities
Get API Key
Create an API key from the Keys page, then set it as an environment variable:
export ONLIST_API_KEY=sk-...Make your first request
Endpoints
https://onlist.io/v1/chat/completionsOpenAI Chat Completions format
https://onlist.io/v1/responsesOpenAI Responses format
https://onlist.io/v1/messagesAnthropic Messages format
Code samples
curl https://onlist.io/v1/chat/completions \
-H "Authorization: Bearer $ONLIST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen/qwen3-4b",
"messages": [
{
"role": "user",
"content": "Explain quantum entanglement in one paragraph."
}
]
}'Replace $ONLIST_API_KEY with the API key from your Keys page.
Authentication
All requests must include an Authorization: Bearer <TOKEN> header. Generate keys from the Keys page; keys can be scoped to specific models, groups, IP ranges, and rate limits.
Enable streaming
Add "stream": true to receive partial responses as server-sent events in real time.
Streaming example
curl https://onlist.io/v1/chat/completions \
-H "Authorization: Bearer $ONLIST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen/qwen3-4b",
"messages": [
{
"role": "user",
"content": "Write a haiku about recursion."
}
],
"stream": true
}'Supported parameters
| Name | Type | Description |
|---|---|---|
tools | array | A list of tools the model may call. Currently supports functions. |
json_mode | ||
streaming | ||
function_calling | ||
structured_outputs |
These are the request parameters this model accepts. Parameter semantics follow the OpenAI Chat Completions specification.