{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "yinxulai-osw--route-requests-to-channel-groups-by-rule",
 "repo": "yinxulai/osw",
 "repo_url": "https://github.com/yinxulai/osw",
 "repo_slug": "yinxulai-osw",
 "title": "Send hard requests to a strong model and easy ones to a cheap model",
 "page_title": "How to send hard requests to a strong model and easy ones to a cheap model with Osw",
 "summary": "Use Smart Routing to split traffic into channel groups by model name, client, or request complexity.",
 "who": "A developer or operator who pays for a strong model and wants routine requests to use a cheaper channel automatically.",
 "problem": "Every request goes to the same default channel, so simple requests use an expensive model and hard requests may not get the stronger one.",
 "outcome": "Requests land in different channel groups according to a rule table or a workflow graph, and each saved policy can be rolled back to an earlier version.",
 "steps": [
  "Set up at least two logical models in OSW with different strengths and costs.",
  "Open Smart Routing and choose between Workflow graph and Rule table in the page header.",
  "In Workflow graph, drop the LLM request complexity policy onto the canvas, or in Rule table, add one rule per condition with its landing channel.",
  "Save the policy and send a few test requests of different difficulty through the OSW address.",
  "Check Request Logs to confirm which channel served each request, then adjust the rules if the split is wrong."
 ],
 "agent_prompt": "Using the OSW repo at yinxulai/osw, build a Smart Routing policy that sends requests matching <condition> to <channel-group> and everything else to the fallback. Expected output: a saved policy and request log rows showing the chosen channel for each test request. Verify with at least one test request per group before reporting the policy as working.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "1 hour",
 "basis": "readme",
 "caveat": "The complexity policy relies on a model to judge difficulty, so it adds a call before routing and its judgments need checking against your own requests.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A Mac, Windows PC, or Linux machine that can run the OSW installer",
  "API keys for at least two LLM channels you own",
  "An AI client that lets you set a custom base URL"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/yinxulai-osw/route-requests-to-channel-groups-by-rule/",
 "md": "https://dedupedai.com/use-cases/yinxulai-osw/route-requests-to-channel-groups-by-rule/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/yinxulai-osw--route-requests-to-channel-groups-by-rule.json",
 "api_version": "v1"
}