Supported models

How the model catalog works, how to list it, and how new models roll out.

Dynoyard exposes a curated catalog of frontier OSS models behind one endpoint. You don’t manage providers or versions — you call a stable dynoyard-side slug and we route it to the best upstream.

The canonical list

The catalog evolves as new models ship, so the canonical source is always live, not this page:

curl https://<your-org>.dynoyard.app/v1/models \
  -H "Authorization: Bearer sk-dyno-XXXX"

Families (mid-2026)

FamilyMakerNotes
KimiMoonshotLong-context, thinking-mode reasoning
MiMoXiaomiReasoning, strong price/performance
DeepSeekDeepSeekR1-style reasoning
QwenAlibabaFlagship qwen-max, fast qwen-plus, MoE variants
GLMZhipuGeneral + agentic

Exact ids and which are enabled on your org always come from /v1/models — don’t hardcode this table.

Capabilities

Each model in /v1/models carries a capabilities array so your SDK or router can light up the right features:

CapabilityMeaning
toolsOpenAI-style function/tool calling
streamingServer-Sent Events streaming
reasoningEmits reasoning_content (thinking mode)
visionAccepts image content blocks (provider-dependent)

This mirrors OpenRouter’s supported_parameters, so catalog-aware tooling (LiteLLM, openrouter-*) reads it without translation.

Slug stability & new models

Choosing a model per request

One key, one endpoint, switch models inline:

for model in ["kimi-k2-thinking", "mimo-v2-5-pro", "qwen-max-3-7"]:
    resp = client.chat.completions.create(
        model=model,
        messages=[{"role": "user", "content": "one-liner intro"}],
    )
    print(model, "→", resp.choices[0].message.content[:80])