Tessary
Tessary custom classifiers
Custom classifiers are classifiers Tessary fine-tunes for your agent. The built-ins cover the failure modes every agent shares. A custom classifier covers the ones only yours has: the policies it must follow, the mistakes it actually makes, the behaviors your team already knows to watch for.
They work like the built-ins: cheap enough to run on every trace, scored against a confidence threshold, and when one fires it creates a finding for further analysis. Each one is trained and evaluated on labeled examples from your own traffic before it ships, and runs at the same negligible per-event cost as the built-ins.
5 questions
Answered, plainly.
Can a custom classifier catch a policy specific to my agent?Yes. A custom classifier is fine-tuned to catch the policies, mistakes, and behaviors specific to your agent that a generic built-in check would never see.answer →What's the difference between a custom classifier and a built-in one?Built-ins run the same check on every customer's traffic; a custom classifier is fine-tuned on your own agent's traffic for failures only your agent has.answer →Does a custom classifier cost more to run than a built-in one?No. A custom classifier runs at the same negligible per-event cost as a built-in classifier, on every trace rather than a sampled subset.answer →Is a custom classifier tested before it goes live?Yes. Every custom classifier is trained and evaluated on labeled examples from your own traffic before it ships and starts scoring live traces.answer →What data trains a custom classifier?Your own agent's production traffic, not a generic public dataset, which is what lets a custom classifier catch the failures only your agent has.answer →