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.
Nex-N2.5-Mini - Model - OpenSmartRoute
Modelv1.0.0
Nex-N2.5-Mini
Nex-N2.5 is an agentic model built to turn goals into working, verified outcomes. Its core strength is agentic coding within a visual feedback loop: it can explore codebases, implement multi-file...
Reference model card from the OpenRouter listing - model nex-agi/nex-n2.5-mini. Prices are per million tokens as listed; ratings and installs below are from this marketplace.
Nex-N2.5-Mini
Nex-N2.5 is an agentic model built to turn goals into working, verified outcomes. Its core strength is agentic coding within a visual feedback loop: it can explore codebases, implement multi-file...
Facts
Vendor
Nex Agi
Context window
262,144 tokens
Max output
235,929 tokens
Input price
$0.03 / 1M tokens
Output price
$0.10 / 1M tokens
Input
text, image
Output
text
Tool calling
no
Structured outputs
yes
Reasoning
yes
Open weights
nex-agi/Nex-N2.5-mini
Endpoint: https://openrouter.ai/api/v1 (OpenAI-compatible), model nex-agi/nex-n2.5-mini
Use it
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://api.opensmartroute.ai/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": "model-nex-agi-nex-n2-5-mini", ...}
Installed into a catalogue, chosen by a router
Install Nex-N2.5-Mini 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.