# AI use cases for Hi Route (higress-group/HiRoute) Repo: [higress-group/HiRoute](https://github.com/higress-group/HiRoute) | Use cases: 4 | Page: https://dedupedai.com/use-cases/higress-group-hiroute/ HiRoute is a local model router that sends routine agent work to economical models and keeps stronger models for hard tasks, while managing subscriptions, API keys, sessions, usage and cost in one place. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Cut Codex and Claude Code costs with difficulty routing: https://dedupedai.com/use-cases/higress-group-hiroute/cut-agent-costs-with-difficulty-routing/ - Route drafting and review to separate model groups: https://dedupedai.com/use-cases/higress-group-hiroute/route-drafting-and-review-to-separate-models/ - Delegate independent tasks to other agents through a Worker plan: https://dedupedai.com/use-cases/higress-group-hiroute/delegate-independent-tasks-to-worker-agents/ - Audit which model ran each agent step and what it cost: https://dedupedai.com/use-cases/higress-group-hiroute/audit-which-model-ran-and-what-it-cost/ ## How to cut Codex and Claude Code costs with difficulty routing with Hi Route Repo: [higress-group/HiRoute](https://github.com/higress-group/HiRoute) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Send routine reading and fact gathering to cheaper models while hard design work stays on your primary model. **Who it is for:** A developer whose Codex or Claude Code subscription runs out early because every step, including simple file reads, uses the strongest model. **The problem:** Agent sessions spend premium model usage on routine steps such as reading code or gathering facts, which drains the subscription quickly. **The outcome:** Routine turns run on an economical model, difficult turns stay on the primary model, and each session shows which model ran and what it cost. ### Steps 1. Run `curl -fsSL https://hiroute.ai/install.sh | sh` to install the current-user CLI and daemon on Linux without sudo. 2. Run `hiroute service start --output json` to start the local service, then run `hiroute system status --output json` to confirm it is running. 3. Connect your Codex or Claude Code subscription, API key, or compatible custom API in Hi Route. 4. Open Models, then Decision models, and connect Bailian, OpenRouter Jev, TypeSafe, or a compatible endpoint. 5. Create and publish a routing plan using difficulty routing, then connect your Agent client to it. 6. Open the sessions view and check the task category, actual model group, and cost for a few turns. ### Prompt to paste into your agent ```text Using the HiRoute repo at https://github.com/higress-group/HiRoute, set up difficulty routing for so routine turns use the regular model group and hard turns use the primary group. Report the published routing plan name and the model group chosen for the last three turns in a session. Verify that the sessions view shows the actual model that ran and its cost. ``` ### Caveat Routing quality depends on the decision model connection you choose, and cache reuse depends on the provider, so savings are not guaranteed. Risk, credentials: Hi Route stores subscription credentials, API keys and decision model connections, so use keys with the minimum permissions you need and review who else can access the local service. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/higress-group-hiroute/cut-agent-costs-with-difficulty-routing/ ## How to route drafting and review to separate model groups with Hi Route Repo: [higress-group/HiRoute](https://github.com/higress-group/HiRoute) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Use custom task branches so drafting and review each get the model that fits their category and difficulty. **Who it is for:** A team lead or developer who wants cheap models for first drafts and a stronger model for review, without one model handling both. **The problem:** A single routing rule cannot tell drafting work from review work, so review either gets an underpowered model or drafting wastes premium usage. **The outcome:** Hi Route picks a task category first, then the simple or complex degree within it, so drafting and review use different model groups. ### Steps 1. Run `hiroute service start --output json` after installing Hi Route, then run `hiroute system status --output json` to confirm the service is up. 2. Connect the decision model you want to use for judgment under Models, then Decision models. 3. Create a routing plan with custom task branches for drafting and review, giving each category a regular group and, where needed, a primary group. 4. Publish the routing plan and connect your Agent client or expose it as a Worker plan. 5. Review the sessions view to confirm each turn shows its category and the model group that actually ran. ### Prompt to paste into your agent ```text Using the HiRoute repo at https://github.com/higress-group/HiRoute, configure a routing plan with separate drafting and review custom task branches for . Report which model group each branch uses and the category HiRoute chose for two sample turns. Verify that a low drafting score does not change the review category. ``` ### Caveat The README describes custom branches but does not list the exact category names or model group limits, so check the routing plan editor before publishing. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/higress-group-hiroute/route-drafting-and-review-to-separate-models/ ## How to delegate independent tasks to other agents through a Worker plan with Hi Route Repo: [higress-group/HiRoute](https://github.com/higress-group/HiRoute) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Hand separate, independent tasks to other agents while Hi Route tracks their execution and cost. **Who it is for:** A developer with several independent tasks, such as separate research or code checks, who wants them run by other agents in parallel. **The problem:** Independent tasks queue behind one agent session, and there is no single place to see what each delegated task used. **The outcome:** Independent tasks run as delegated Worker work, and each execution appears in local session views with its model, usage and cost. ### Steps 1. Install Hi Route on Linux with `curl -fsSL https://hiroute.ai/install.sh | sh`, then start it with `hiroute service start --output json`. 2. Create an agent work plan that defines the independent tasks you want delegated. 3. Expose a Worker plan for those tasks and publish it. 4. Connect the delegating Agent client to the Worker plan. 5. Open the sessions view and review each delegated task's category, model group and result. ### Prompt to paste into your agent ```text Using the HiRoute repo at https://github.com/higress-group/HiRoute, expose a Worker plan that delegates to other agents. Report the status and model group of each delegated task. Verify that each delegated execution appears in the local session view with its usage and cost. ``` ### Caveat The README says independent tasks can be delegated but does not name the delegation targets beyond connected agents, so confirm which agents your Worker plan can reach. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/higress-group-hiroute/delegate-independent-tasks-to-worker-agents/ ## How to audit which model ran each agent step and what it cost with Hi Route Repo: [higress-group/HiRoute](https://github.com/higress-group/HiRoute) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Check per-session model, usage and cost so you can tune routing with real execution data. **Who it is for:** A developer or team lead who suspects routing is not saving money and needs evidence from actual sessions. **The problem:** Without per-step records, it is unclear which model handled each turn, how much usage it used, and whether routing changed the outcome. **The outcome:** A list of sessions showing the task category, actual model group, tool outcomes, usage and cost, which you can use to adjust the routing plan. ### Steps 1. Run `hiroute service start --output json` if the service is not running, then run `hiroute system status --output json` to confirm. 2. Run agent sessions through your connected Agent client as usual. 3. Open the sessions view in Hi Route and filter for a recent session. 4. Check the task category, actual model group, usage and cost recorded for each turn. 5. Adjust the difficulty routing thresholds or custom branches in the routing plan based on what you see. ### Prompt to paste into your agent ```text Using the HiRoute repo at https://github.com/higress-group/HiRoute, review the most recent session for and list each turn's task category, actual model group, usage and cost. Verify that the model shown is the one that actually ran, not the one the routing plan intended. ``` ### Caveat The README describes the session and cost views in general terms, so exact field names and export options may differ from what you see in the app. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/higress-group-hiroute/audit-which-model-ran-and-what-it-cost/