Browse documentation

Answer quality

Evaluate the answer your application receives.

Define a useful answer

Use prompts representative of your application and decide what counts as a correct or useful response before comparing systems. Use known answers, executable checks or human review as appropriate.

Check behavior as well as text

For structured output, validate the schema. For coding, run the relevant tests. For tools, check the arguments and the final outcome. Record incomplete answers and errors as part of the result.

Keep the quality bar consistent

Apply the same criteria to direct model responses and tlc responses. A lower bill is only useful alongside acceptable answer quality.

The Transductor is in early access. Join the waitlist.