Legal · use case
Contracts and filings route to large-context, high-reasoning models; a confidence floor sends any low-certainty answer to counsel instead; data-boundary rules keep privileged documents off public endpoints; every decision is on the record for the matter file.
Free plan, no card. Self-hosting is free forever; the rules below run the same way on both.
The situation
Legal work is long documents, high stakes and confidentiality. A cheap model misses a clause; a frontier model on every e-mail is wasteful; and the answer a lawyer must not rely on looks exactly like the one they can - unless the router says how sure it was and hands the doubtful ones to a person.
What changes
One request
Long contracts go to large-context models; a confidence floor routes low-certainty answers to counsel.
The policy
This is the rules.yaml that produces the behaviour above; targets.yaml names the models, agents and people it refers to. The floor is one router setting: below min_confidence the request goes to fallback_target instead.
rules:
- name: contracts-need-context
when:
domains: [legal]
min_complexity: 0.5
prefer: [llm-frontier]
weight: 0.8
- name: anything-doubtful-to-counsel
when:
domains: [legal]
actions: [escalate]
prefer: [counsel-review]
pin: true
# router settings:
# min_confidence: 0.55
# fallback_target: counsel-reviewExample: Illustrative configuration or synthetic data, not a customer's.A reference configuration to start from - rules the router enforces as written, not a description of how a named customer runs it.
OpenSmartRoute is open source and the free plan keeps the full trace of every decision. Create a workspace, paste the rules, route a request.
Free plan, no card. Fifteen thousand decisions a month with the full trace.