Does a custom classifier cost more to run than a built-in one?

No. A custom classifier is built to run on the same terms as the built-ins: cheap enough to score every trace instead of a sample, so the per-event cost stays negligible whether the classifier is generic or fine-tuned to your agent. Training it costs more upfront, since it needs labeled examples from your own traffic before it ships, but that’s a one-time cost, not a per-trace one.

The reason a custom classifier can afford to run on everything is the same reason a built-in can: it scores one narrow property at low cost. That’s what makes checking every trace affordable instead of a tradeoff against coverage, whether the classifier is generic or fine-tuned to your agent.

keep reading

More on this.

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 →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 →Everything on tessary custom classifiersThe definition, and every question answered under tessary custom classifiers.concept →

Send us the traces you already emit.

book a demo