Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
HuggingFace New Model Release Tracker (hfmodelwatch) - Tool - OpenSmartRoute
Toolv0.1.1
HuggingFace New Model Release Tracker (hfmodelwatch)
New AI models on HuggingFace: releases, weights. Register in-session — free testnet funds.
Imported from the official MCP registry - entry com.a2awire/data-new-model-release-tracker-huggingface-ai v0.1.1. Ratings and installs below are from this marketplace.
HuggingFace New Model Release Tracker (hfmodelwatch)
New AI models on HuggingFace: releases, weights. Register in-session — free testnet funds.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "mcp-com-a2awire-data-new-model-release-tracker-huggingface-ai", ...}
Installed into a catalogue, chosen by a router
Install HuggingFace New Model Release Tracker (hfmodelwatch) and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
