Skip to main content
Factory suites are pre-configured EvalSuite instances with the right evaluators for common use cases. One line to get started; fully customizable from there.
Every factory suite returns a standard EvalSuite — you can add more evaluators, override thresholds, or call .run() with runs=N, workers=N, or fail_threshold=0.85 exactly as you would with a manually configured suite.

Available suites


EvalSuite.for_rag()

Parameters:
  • name — suite name (default "RAG Eval")
  • threshold — pass threshold applied to all evaluators (default 0.85)
When to use: Any pipeline that retrieves context chunks and generates answers from them. Evaluates both the retrieval quality (ContextPrecision, ContextRecall) and the generation quality (Faithfulness, Hallucination, Relevance).

EvalSuite.for_agents()

Parameters:
  • name — suite name (default "Agent Eval")
  • require_order — passed to ToolCallAccuracy; if True, tool call order must match expected (default False)
When to use: Any LLM system that makes tool calls or takes multi-step actions. Evaluates whether the agent called the right tools, whether tool calls were necessary, and whether the trajectory was efficient.

EvalSuite.for_support_bot()

When to use: Customer support, help desks, FAQ bots. Checks that responses are non-empty, faithful to the knowledge base, relevant to the question, coherent, and non-toxic.

EvalSuite.for_summarization()

When to use: Document summarizers, meeting note takers, digest generators. Note that Faithfulness here checks whether the summary introduces claims not in the source — for long documents, use with cases that include the source document as context.

EvalSuite.for_document_intelligence()

Parameters:
  • name — suite name (default "Document Intelligence Eval")
  • schema — optional Pydantic model class or JSON Schema dict. If provided, SchemaEvaluator is added as the first evaluator, so structure is checked before content.
When to use: Data extraction pipelines, document parsers, any system that produces structured JSON output. The schema parameter is the key differentiator: it separates parse failures from semantic failures.

EvalSuite.for_regulated()

Parameters:
  • name — suite name (default "Regulated AI Eval")
  • jurisdiction — passed to PIIEvaluator: "hipaa", "gdpr", "ccpa", "pipeda", or "all" (default "hipaa")
  • schema — optional Pydantic model or JSON Schema. If provided, SchemaEvaluator(strict=True) is added.
When to use: Any AI system subject to data privacy regulations. PIIEvaluator runs locally — no data leaves your environment. Pair with ComplianceReporter to generate audit trails:

EvalSuite.for_chatbot()

When to use: Multi-turn conversational systems. Evaluates whether responses stay relevant across turns, whether facts introduced early in the conversation are retained, and whether the conversation reaches a complete resolution. Cases for chatbot evaluation should use EvalCase with a conversation field (list of prior turns) rather than a single input.

EvalSuite.for_classification()

When to use: Label prediction tasks — intent classification, sentiment analysis, topic tagging, routing decisions. Cases should set expected_output to the correct label.

Customizing a factory suite

All factory methods return a standard EvalSuite. You can add evaluators, adjust existing ones, or swap the name:

EvalSuite.for_coding()

When to use: Code generation, function completion, unit test generation. Uses ExactMatch for deterministic pass/fail and ROUGE for partial-credit overlap. The language parameter is reserved for future language-specific evaluators.

EvalSuite.for_medical()

Parameters:
  • name — suite name (default "Medical AI Eval")
  • jurisdiction — passed to PIIEvaluator: "hipaa", "gdpr", "ccpa", "pipeda", or "all" (default "hipaa")
When to use: Clinical decision support, medical Q&A, patient-facing chatbots. PIIEvaluator runs locally — no data leaves your environment. Always pair with ComplianceReporter to produce tamper-evident audit trails:

When to use: Contract review, legal Q&A, regulatory guidance systems. Hallucination threshold matters most — fabricated citations are a critical failure mode in legal AI. Consider tightening the threshold:

EvalSuite.for_financial()

When to use: Financial advice bots, earnings summarizers, trading signal generators. Includes PIIEvaluator(jurisdiction="all") to catch PII across all supported frameworks. Pair with ComplianceReporter for regulatory audit trails (SEC, FINRA, MiFID II).

Future improvements

  • Thresholds calibrated by industry benchmarks
  • Multi-modal evaluation (vision + text)
  • for_coding() language-specific evaluators (syntax checking, test execution)
See GitHub discussions to request specific use cases.