NIN-Route-v1
Give each request a suitable path.
Discuss this model ↗Upcoming model. Capabilities describe our plans; weights and inference are not available.
Give each request a suitable path.
Route requests to suitable tools and workflows.
Choose a suitable tool or workflow from an allowed set.
Use request context to distinguish search, writing and other tasks.
Send unclear requests back for clarification when a path cannot be selected safely.
See the intended workflow.
Illustrative example, authored by NIN. This is not a live model prediction.
Request + available workflows
Find my notes about the launch. Workflows: workspace_search, draft_text.
Selected path
{
"workflow": "workspace_search",
"query": "launch"
}Routing selects a path; tool execution and access checks belong to the host application.
Local NINXL
Built around your workflow.
Local execution inside NINXL is the intended deployment. The host application will control tools, permissions and workflow boundaries.
Details after evaluation.
Model size, hardware requirements, supported formats, licensing and measured performance will be documented when available. No release date is announced.
Where could NIN-Route-v1 help?
Tell us about your workflow, the data it uses and what a useful result would look like. Discuss an evaluation partnership with NIN.
Discuss this model ↗