Unverified50% confidenceFactExact time
Using Decision Models requires upgrading to version 0.3.5 or higher, pulling the Nimble model, and sending a POST request to the /decision endpoint; no API key is required for local requests.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/7/2026
First Seen
Valid until: 1/5/2027
Sources
Related Entities
Related Claims
UnverifiedWhen making API calls, a specific model version number rather than a generic alias should be specified to avoid being automatically routed to a new version; however, even with a locked version number, the service provider may still adjust underlying behavior without changing the version identifier.61% similarUnverifiedThe core change in version 2.0.49 is to retain reasoning content across multi-turn requests by default on supported models.59% similarUnverifiedBehind the same API endpoint of a closed-source large model, there may be different versions that have undergone weight updates, quantization compression, or inference parameter adjustments, and such changes are typically not disclosed to users.58% similarUnverifiedWhen a tool schema changes but the corresponding instruction descriptions in the prompt are not updated in sync, the model may generate malformed tool call requests, leading to runtime exceptions.57% similarUnverifiedVersion 5.0.16 adds a portable max reasoning level at the provider layer, with native provider mapping, compatibility coercion, and budget-based fallback support57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/984292API
curl https://kongchang.com/api/v1/knowledge/claims/984292MCP
get_claim(id=984292)