Latest Model Resolution

Not yet available.

Model families — like Claude, Gemini, and Llama — release new versions regularly. The Latest Model Resolution feature lets you pin to a moving :latest alias instead of a fixed version slug. When a new version is added to the catalog, your requests automatically route to it with no code change.

Usage#

Append :latest to a model family prefix:

curl https://opendunes.com/api/v1/chat/completions \
  -H "Authorization: Bearer $OPENDUNES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "anthropic/claude:latest",
    "messages": [{ "role": "user", "content": "What changed in the latest Claude model?" }]
  }'

The model field in the response always reflects the resolved concrete slug (e.g., anthropic/claude-opus-4.8), so you always know what ran.

Alias formats#

Aliases always resolve to the latest stable release. Release candidates and beta models are excluded unless you explicitly opt in (opt-in not yet available).

Resolution rules#

"Latest" is determined by the catalog's publish date for each model slug. OpenDunes resolves the alias at request time using the current catalog snapshot:

1. Find all models matching the provider/family prefix (e.g., anthropic/claude-*).
2. Exclude deprecated or inactive models.
3. Return the most recently published model in that set.

Resolution adds negligible overhead — the result is cached in the routing layer.

Stable vs. bleeding edge#

The :latest alias tracks the stable catalog. If you want to test a newly added model before it becomes :latest, reference it by its full slug directly. There is no separate :beta or :preview alias in this release.

Caveats#

Using :latest trades predictability for currency:

• Output may change — different model versions have different capabilities, style, and behavior. If you need reproducible outputs, pin to a specific slug (e.g., anthropic/claude-sonnet-5).
• Cost may change — newer models are often priced differently. Monitor your DA usage after a resolution change.
• Resolution changes are not announced per-request — check the resolved model field in the response if you need to detect when a new model was picked.

For production workloads where consistency matters, use a pinned slug. Use :latest for applications where you always want the newest capability (chatbots, assistants, exploratory tools).

Checking the current resolution#

To see what :latest resolves to right now without making an inference request:

GET /api/models/anthropic/claude:latest

The response is the full model object for the currently resolved slug, including its exact name, context length, and DA pricing.

Using with the OpenAI SDK#

import os
from openai import OpenAI

client = OpenAI(
    base_url="https://opendunes.com/api/v1",
    api_key=os.environ["OPENDUNES_API_KEY"],
)

resp = client.chat.completions.create(
    model="anthropic/claude:latest",
    messages=[{"role": "user", "content": "Write a haiku about Algeria."}],
)
print(resp.choices[0].message.content)
print("Resolved to:", resp.model)