Skip to main content
Dahl exposes models through the OpenAI-compatible GET /v1/models endpoint. Always read IDs from the live response — IDs can change as the Gonka network adds or rotates capacity.

Currently available

These models are typically returned from production (verify with GET /v1/models): The landing page shows the same model IDs in copy-paste curl examples (MiniMax, Kimi, and DeepSeek tabs). Only the model field changes between them.

Default choice

Start with MiniMax M2.7 (MiniMaxAI/MiniMax-M2.7). It is the default in the Dahl chat UI and matches the examples on inference.dahl.global.

Using a model in chat completions

Set the model field to the exact id string from GET /v1/models. All requests require Authorization: Bearer (see API keys). MiniMax M2.7:
Kimi K2.6 — same request shape, different model value:
DeepSeek V4 Flash — same request shape, different model value:

Model availability

GET /v1/status reports recent probe results per model (uptime and operational flag). It is public — no API key required.
Supported window values: 1h, 24h, 7d, 30d (default 24h if omitted). Example response shape:
Use this when a model appears in GET /v1/models but requests fail or time out — the status page and this endpoint reflect the same probe data.

Streaming

Add "stream": true to the JSON body for token streaming. Dahl forwards streaming responses from the upstream network in OpenAI SSE format (data: {...} lines, ending with data: [DONE]). Streaming uses the same Authorization: Bearer header and model id as non-streaming requests. For long completions, streaming is usually preferable so your client can render tokens as they arrive instead of waiting for the full response body.
When the upstream includes usage metadata in the stream, successful requests also update your key balance (see Check remaining balance). Manage keys and usage at inference.dahl.global/account.

When a model fails

If you receive a 4xx or 502 mentioning the model:
  1. Call GET /v1/models again
  2. Check GET /v1/status for recent uptime
  3. Switch to an id present in the response
  4. Retry with short backoff if the network reports overload (503 or timeouts)
See Quickstart for a full first-request walkthrough.