LangChain Launches Tuned Evaluators to Cut LLM Judge Costs
LangChain has launched Tuned Evaluators for LangSmith to help developers automatically flag errors in production AI conversations at a fraction of the cost of frontier LLM judges.

LangChain has released Tuned Evaluators, a new feature for its LangSmith agent engineering platform designed to automate quality feedback on production traces. The system launches with its first specialized evaluator, Perceived Error, which identifies when an AI agent has misunderstood a user, made a mistake, or misdirected a conversation. Instead of requiring developers to write complex prompts or manage LLM-as-a-judge infrastructure, LangChain handles the entire evaluation pipeline end-to-end.
To address the traditional trade-off between evaluation accuracy and cost, LangChain post-trained a specialized model specifically for the Perceived Error metric. In internal benchmarks, this specialized judge outperformed every frontier model while slashing evaluation costs by up to 82%. For some early partners, the cost savings reached as high as 98%, depending on the composition of the message threads.
For practitioners, the workflow is highly automated. Once a Tuned Evaluator is attached to a LangSmith tracing project, the platform automatically identifies eligible threads. A conversation becomes eligible for the Perceived Error evaluator once it contains at least two human-AI message pairs and has remained idle for a configured period. The system then runs the specialized judge and attaches the score and an explanation to the trace within 12 hours.
This setup allows engineering teams to monitor entire production workloads rather than relying on small, manual samples. Kevin Royer, a staff ML/AI engineer at early partner Vanta, called the tool "the fastest way we've found to make a team operational on quality." The Perceived Error Tuned Evaluator is currently available to users on LangSmith Plus and Cloud Enterprise plans in the United States, with billing applied only to successful evaluations.
This is our own summary of reporting by LangChain Blog



