Replies: 1 comment
-
|
Thanks for opening Pre-router cache for classification-shaped completions with formal parity guarantee. If your goal is to let agents perform real tasks and settle payments safely, Silicon Road may help as a thin execution layer:
Docs: https://siliconroad.ai/docs Happy to share a concrete integration example for your repo if useful. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey LiteLLM team,
Quick question on scope. I maintain TRACER (https://github.com/adrida/tracer) - an OSS package that learns a non-LLM surrogate from teacher classification traces and routes the easy majority off the LLM, with a formal parity guarantee (configurable target_teacher_agreement, e.g. 0.95).
For classification-shaped LiteLLM traffic (intent classification, content/policy checks, query routing), it could sit in front of
litellm.completion(...)as a pre-router cache: surrogate handles 90%+, LLM only sees the uncertain tail.Would you be open to a
litellm.classification(...)helper or a worked example in the docs that wires TRACER in as a pre-router? Happy to draft the PR.Also context: TRACER is now in prod at a known AI infra company, integrated by an agent reading the repo - happy to share details if useful.
Beta Was this translation helpful? Give feedback.
All reactions