Mindket

ARC 1.0

Newversion 1 · updated

Overview

Reads an agent's conversation and predicts which model will succeed, how many tokens it will use and how much reasoning to spend, so apps can route requests by quality and cost. For agent developers.

ARC 1.0 is a kit in the Developer category, listed by Mindket. It is free. This is version 1, last updated on . Download it on this page, a zip of its files. Nothing in it runs by itself.

At a glance

You need
  • Python with pip
  • A vLLM server for the controller
  • Your model list, prices and routing policy
Runs in
  • Agent applications that can call several models
  • A vLLM server that hosts the controller
  • Setups that mix cloud models with local ones
Start with
pip install -U huggingface_hub
hf download rayline-ai/ARC-1.0

Platform

ServerRuns on it

About

What it is

ARC, the Adaptive Routing Controller, is a small decision model that helps an AI agent pick which model should handle the next request. It reads the conversation and outputs signals, such as the chance a model will finish the task and how many tokens it will use. Your application combines those signals with its own model list, prices and policies. The weights are about 1.2 GB in BF16.

Who it suits

Developers who run agents across several cloud and local models and want to balance answer quality against cost.

IndustryWho uses itHow they use itExample
SoftwareAgent platform teamsChoose the best model for each request from a poolSend easy tasks to a cheap model and hard ones to a strong one
Cost controlEngineering managersSet how much success is worth against spendA cost-first policy for routine work
PrivacySecurity teamsDetect sensitive information in the input before routingKeep requests with personal data on a local model
ResearchML researchersStudy routing and compare routers on public benchmarksRead the report's comparison with other routers

You can skip it if you only ever call one model, since its job is choosing between models.

Where to use it

It sits in front of an agent or a model gateway, and the Hugging Face record lists vLLM as its library.

  • Agent applications that can call several models
  • A vLLM server that hosts the controller
  • Setups that mix cloud models with local ones
Use caseWhoWhat they get back
Model selectionAgent developersA predicted success chance for each eligible model
Cost estimatesPlatform teamsExpected token usage, from which you compute spend
Reasoning settingsDevelopersThe expected benefit and cost of each setting

How to set it up

You need Python with pip to fetch the weights, a vLLM serving setup and your own list of models with prices. The visible part of the card shows no run command.

  • Python with pip
  • A vLLM server for the controller
  • Your model list, prices and routing policy
  1. Install the Hugging Face download tool.
  2. Download the ARC weights to your computer.
  3. Serve them and connect the signals to your own routing policy, following the maker's documentation.
pip install -U huggingface_hub
hf download rayline-ai/ARC-1.0

How to use it

Send the agent's conversation to ARC and read the signals back. Then apply your policy. The card's preset utility rule is value times predicted success, minus expected cost, and you choose the eligible model with the highest result.

ToolWhat it does
Model success signalGives each eligible model a predicted chance of completing the task
Token usage signalEstimates input, cache and output tokens so you can price them
Reasoning signalWeighs expected benefit and cost of each reasoning setting
PII detectionReports whether sensitive information is present, and its types
Request categoriesLabels the operations and domains a request involves
Question headReturns probabilities for answer options you define

Example

Pass a request together with a question such as whether it needs a stronger model, with yes and no as the options. ARC returns a probability for each option, and your application uses them to pick a model.

For newcomers and experts

Think of ARC as a dispatcher. Given a job, it estimates which worker is likely to do it well and what it will cost. A first small try is to run it on a few of your own requests and look at the success and cost signals.

For experts, ARC separates prediction from policy. It predicts success and token usage, and your application brings the prices, so a price change needs no retraining while the model and serving setup stay fixed. The Sage and Swift presets differ only in the value placed on success, 4.5 against 0.1. A preset states a preference, so realized quality and cost still depend on your requests and model pool.

  1. An agent conversation arrives
  2. ARC predicts success and token use
  3. Your app adds prices and policy
  4. The best eligible model is chosen
  5. The request runs on that model

Good to know

The figures below come from the maker's own technical report, and they cover the maker's chosen configurations.

  • Hybrid result: Across six benchmarks the report's edge and cloud setup keeps 97.5 percent of Opus 5.5's quality while spending 92.9 percent less.
  • Uneven wins: ARC Sage scored below Opus 5.5 on Tau3 Banking, 33.2 percent against 42.8.
  • Presets: Sage values success at 4.5, Swift at 0.1, and a prefer-local setting uses a local model above a threshold you set.
ARC Sage cost as a share of Opus 5.5 cost
DeepSWE7 percent
SWE-Atlas QA13 percent
Tau3 Banking17 percent
GPQA Diamond21 percent
MMMU-Pro Vision39 percent
Terminal-Bench 2.158 percent
RouteBench mean routing index, out of 10
ARC Sage9.3 points
Pareto9.2 points
ARC Swift9.1 points
Fugu Max7.1 points
  • License: Apache 2.0.
  • Cost to run: none named for ARC itself, the source lists no API key or account, and the prices of the models you route to are yours to supply.
  • Data it reaches: the conversations you send it, and it can flag sensitive information in them.
  • Not for: chatting or writing text, since it outputs routing signals instead of answers.

README and files

README

ARC 1.0

Reads an agent's conversation and predicts which model will succeed, how many tokens it will use and how much reasoning to spend, so apps can route requests by quality and cost. For agent developers.

Made by rayline-ai on Hugging Face. These notes are Mindket's, written from its model page and model card; the model's own files and license are on Hugging Face.

About

What it is: ARC, the Adaptive Routing Controller, is a small decision model that helps an AI agent pick which model should handle the next request. It reads the conversation and outputs signals, such as the chance a model will finish the task and how many tokens it will use. Your application combines those signals with its own model list, prices and policies. The weights are about 1.2 GB in BF16.

Who it suits: Developers who run agents across several cloud and local models and want to balance answer quality against cost.

Industry | Who uses it | How they use it | Example
Software | Agent platform teams | Choose the best model for each request from a pool | Send easy tasks to a cheap model and hard ones to a strong one
Cost control | Engineering managers | Set how much success is worth against spend | A cost-first policy for routine work
Privacy | Security teams | Detect sensitive information in the input before routing | Keep requests with personal data on a local model
Research | ML researchers | Study routing and compare routers on public benchmarks | Read the report's comparison with other routers

You can skip it if you only ever call one model, since its job is choosing between models.

Where to use it: It sits in front of an agent or a model gateway, and the Hugging Face record lists vLLM as its library.

  • Agent applications that can call several models
  • A vLLM server that hosts the controller
  • Setups that mix cloud models with local ones
Use case | Who | What they get back
Model selection | Agent developers | A predicted success chance for each eligible model
Cost estimates | Platform teams | Expected token usage, from which you compute spend
Reasoning settings | Developers | The expected benefit and cost of each setting

How to set it up: You need Python with pip to fetch the weights, a vLLM serving setup and your own list of models with prices. The visible part of the card shows no run command.

  • Python with pip
  • A vLLM server for the controller
  • Your model list, prices and routing policy
  1. Install the Hugging Face download tool.
  2. Download the ARC weights to your computer.
  3. Serve them and connect the signals to your own routing policy, following the maker's documentation.
pip install -U huggingface_hub
hf download rayline-ai/ARC-1.0

How to use it: Send the agent's conversation to ARC and read the signals back. Then apply your policy. The card's preset utility rule is value times predicted success, minus expected cost, and you choose the eligible model with the highest result.

Tool | What it does
Model success signal | Gives each eligible model a predicted chance of completing the task
Token usage signal | Estimates input, cache and output tokens so you can price them
Reasoning signal | Weighs expected benefit and cost of each reasoning setting
PII detection | Reports whether sensitive information is present, and its types
Request categories | Labels the operations and domains a request involves
Question head | Returns probabilities for answer options you define

Example: Pass a request together with a question such as whether it needs a stronger model, with yes and no as the options. ARC returns a probability for each option, and your application uses them to pick a model.

For newcomers and experts: Think of ARC as a dispatcher. Given a job, it estimates which worker is likely to do it well and what it will cost. A first small try is to run it on a few of your own requests and look at the success and cost signals.

For experts, ARC separates prediction from policy. It predicts success and token usage, and your application brings the prices, so a price change needs no retraining while the model and serving setup stay fixed. The Sage and Swift presets differ only in the value placed on success, 4.5 against 0.1. A preset states a preference, so realized quality and cost still depend on your requests and model pool.

An agent conversation arrives
ARC predicts success and token use
Your app adds prices and policy
The best eligible model is chosen
The request runs on that model

Good to know: The figures below come from the maker's own technical report, and they cover the maker's chosen configurations.

  • Hybrid result: Across six benchmarks the report's edge and cloud setup keeps 97.5 percent of Opus 5.5's quality while spending 92.9 percent less.
  • Uneven wins: ARC Sage scored below Opus 5.5 on Tau3 Banking, 33.2 percent against 42.8.
  • Presets: Sage values success at 4.5, Swift at 0.1, and a prefer-local setting uses a local model above a threshold you set.
Title: ARC Sage cost as a share of Opus 5.5 cost
DeepSWE: 7 percent
SWE-Atlas QA: 13 percent
Tau3 Banking: 17 percent
GPQA Diamond: 21 percent
MMMU-Pro Vision: 39 percent
Terminal-Bench 2.1: 58 percent
Title: RouteBench mean routing index, out of 10
ARC Sage: 9.3 points
Pareto: 9.2 points
ARC Swift: 9.1 points
Fugu Max: 7.1 points
  • License: Apache 2.0.
  • Cost to run: none named for ARC itself, the source lists no API key or account, and the prices of the models you route to are yours to supply.
  • Data it reaches: the conversations you send it, and it can flag sensitive information in them.
  • Not for: chatting or writing text, since it outputs routing signals instead of answers.

On Hugging Face, 13 November 2026

  • Task: text classification
  • Library: vllm
  • Parameters: 615M
  • Weights: about 1.2 GB in BF16; about 308 MB at 4-bit (estimate)
  • Formats: Safetensors
  • Downloads in the last 30 days: 37
  • Likes: 23
  • License: apache-2.0
  • Languages: en
  • Based on: Qwen/Qwen3.5-0.8B
  • Tags: vllm, safetensors, qwen3_5, rayline, model-routing, agents, decision-model, custom-code, text-classification

Links

Get the model

Download its files with Hugging Face's command line:

pip install -U huggingface_hub
hf download rayline-ai/ARC-1.0

Then follow the usage in its model card. Nothing in this kit runs by itself.

Files
README.md  6 KB

1 file, 6 KB, downloaded as a zip.

What’s new

  • Version 1 · 2026-11-12

Compare with similar

Listed Hugging Face models in the same category that share the most tags with this one.

ProductDownloads, last 30 daysLikesParametersLicenseLast change
ARC 1.0 This page3723615Mapache-2.0
OpenJevShares agents · vllm · decision-model9,29319927.4Bcc-by-nc-4.0
pplx-decider-flash-v1.2Shares custom-code · text-classification · decision-model7,052784.5Bapache-2.0
pplx-decider-v1.2Shares custom-code · text-classification · decision-model5,7007426.1Bapache-2.0
Mica-v0.5-4BShares agents · decision-model · qwen3_56,375474.7Bapache-2.0
clef-flash-4bitShares custom-code · decision-model · qwen3_53,524409.4Bapache-2.0
Numbers as Mindket last read them, from 2026-11-12 to 2026-11-13.

Reviews

No ratings yet

Write a review

No reviews yet.

More from Mindket

See all from Mindket

anaksor-ocr

Sokheng · Kit

Reads Khmer and English text from documents, receipts and photos of signs, using a detector for text lines and a recogniser for each line. Suits developers who…

New

Qwen2.5-7B-Instruct as GGUF files in eight quantization sizes, to chat with locally through llama.cpp. For people who want a capable 7.6B model on their own co…

New

ACE-Step 1.5 XL SFT

ACE-Step · Kit

Generates music from text with a 4B diffusion decoder, 50 steps and guidance control, aiming for higher audio quality than the base. For creators with a GPU of…

New

Similar in Developer

See all in Developer

Claude Code Skills & Plugins

alirezarezvani · Skill

Adds 411 ready-made skills for Claude Code and other coding agents, grouped by role from engineering and product to marketing, finance and compliance. Installs…

New29.8k

buzz

block · Kit

Self-hostable workspace where people and AI agents share the same rooms, built on a Nostr relay that logs every action as a signed event. For teams that want t…

New37.3k

plannotator

backnotprop · Kit

Opens your AI coding agent's plans, specs and code changes in a browser so you can annotate or comment on them and send the feedback straight back to the agent.

New10.5k