Example
curl https://api.luv13.ai/v1/models \
-H "Authorization: Bearer $LUV13_API_KEY"Sending your key is harmless and keeps the call working if luv13 starts requiring it. On 2026-09-30 the same call without the header also returned HTTP 200.
The response
The live response on 2026-09-30, trimmed to two of the seven entries:
{
"data": [
{"created": 1700000000, "id": "luv13/deepseek-v4-pro", "object": "model", "owned_by": "luv13"},
{"created": 1700000000, "id": "luv13/deepseek-v4.1-flash", "object": "model", "owned_by": "luv13"}
],
"object": "list"
}| Field | What it holds on luv13 |
|---|---|
object (top level) | list |
data | One entry per model |
id | The model id, such as luv13/kimi-k3. Use it as model in requests. |
object (per entry) | model |
created | 1700000000 for every model. It's the same fixed value for all seven, so don't read it as the date a model was added. |
owned_by | luv13 for every model |
The full list on 2026-09-30 was luv13/deepseek-v4-pro, luv13/deepseek-v4.1-flash, luv13/glm-5.3, luv13/glm-5.3-flash, luv13/kimi-k3, luv13/kimi-k3-fast and luv13/qwen-3.8-27b.
Each model has its own page: DeepSeek V4-Pro, DeepSeek V4.1 Flash, GLM 5.3, GLM-5.3 Flash, Kimi K3, Kimi K3 Fast and Qwen 3.8 27B.
The response has no context length, modality or price fields. Those are on the model list at Models and on Pricing.
To print only the ids:
curl -s https://api.luv13.ai/v1/models | jq -r '.data[].id'Why it matters
Most OpenAI-compatible tools call this endpoint to fill their model picker. If a tool shows no models, check the base URL first; it must be exactly https://api.luv13.ai/v1. See Base URL.
There's no single-model endpoint: GET /v1/models/luv13/kimi-k3 returns HTTP 404. Filter the list instead.
