QAVE Studio Docs
QAVE Studio Docs
Sign inGet started — the Studio loop
Getting StartedFirst assurance runQuick assure
ConceptsLifecycleGlossaryHow QAVE Studio worksComing soon
Account & workspaceSignup and loginPeopleDemo creditsRolesSettings
Generate simulation suitesContext templatePII and field enhanceDimensionsAgents and plannerDraft review and Save
ExportExport formatsExport formats (detail)
Assurance SDKSDK overviewQAVE Studio suite fetch APIAgent and JSONL queueLangfuse bridge
Execute and tracesRecipe chatbot (reference SUT)TracingFetch tracing
AssureEvaluate APIRubrics and evidenceReading scores
History
WorkbenchGolden data
CoverageCoverage dashboardCoverage strategiesCoverage advisorTest case quality
RAG AssuranceRAG runsRAG datasetsRAG analytics
Project evalsError analysisUnderstanding scores
Studio guidesDimensionsTuplesConversation modesMulti-lingual testingWorkflowsHuman reviewBest practices
ReferenceAPI and packagesTroubleshooting
Concepts

Glossary

Map friendly QAVE Studio terms to API and package names.

Docs termMeaningCode / API
QAVE StudioUser-facing product name—
AssuranceScoring a trace against a Criterion/v1/assure/evaluate, “evaluate” in APIs
Simulation suiteApproved set of casesTestSuite
Case / draft caseIndividual scenariosuite cases / generation drafts
Criterion / rubricWhat “good” means for scoringCriterion model, rubrics APIs
EvidenceWhy the score is what it isevidence_for, evidence_against
HistoryPast assurance runs/history, /v1/assure/history/evaluations
WorkbenchSME review surface/v1/workbench/*
Assurance SDKExecute + normalize + assure runtimequrator / qurator-sdk-agent packages
SUTSystem under teste.g. recipe-chatbot POST /api/chat
QuratorName you may see in APIs and packages for the assurance gatewayGateway services

Lifecycle

The assurance loop from simulation suite to scored history and golden data.

How QAVE Studio works

Short mental model for the Studio assurance lifecycle.