Add :exacto to a model to prefer the providers that call tools most reliably.
:exacto asks for quality-first provider ordering on one model. Instead of the default, price-weighted order, the providers with the strongest tool-calling record go first, those with little data after them, and the weak ones last.
curl https://opendunes.com/v1/chat/completions \
-H "Authorization: Bearer $OPENDUNES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "anthropic/claude-sonnet-5:exacto",
"messages": [{ "role": "user", "content": "Book the cheapest Algiers–Oran flight on Friday." }],
"tools": []
}'provider.sort: "exacto" does the same without the suffix. Fallback models in models may carry :exacto too.
The same signals as Auto Exacto: the tool-call error rate on real traffic, throughput and latency, and each endpoint's benchmark scores.
| Runs | |
|---|---|
| Auto Exacto | by itself, on every request that carries tools |
:exacto | when you ask for it, on any request |
On a model that calls tools, that several providers serve, and whose providers differ in how well they do it — an agent's loop, where one malformed tool call costs a turn. :exacto changes the order of providers, never the model or its price list: you pay the endpoint that served, in DA.
Among :nitro, :floor and :exacto, the last one named wins: model:nitro:exacto sorts by quality.