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
Getting Started

Getting Started

Tutorial paths for your first successful QAVE Studio assurance loop.

The docs home is the Studio-loop map (Setup Wizard → execute → Assurance Lab). Use this section when you want a tutorial path with concrete steps.

Choose your path

PathBest whenGuide
First assurance runFull platform story: generate → export → exercise SUT → assure → HistoryFirst assurance run
Quick assureYou already have a conversation/trace and want scores fastQuick assure
SDK runtimeYou are wiring CI/CD or in-VPC executionAssurance SDK

Prerequisites

  • A QAVE Studio project (sign up / sign in) — only needed to run Studio, not to read the docs
  • Optional: the recipe-chatbot reference SUT for local tutorials (Execute)
  • Optional: Langfuse (or paste traces) for the fetch path

What “done” looks like

You can point to:

  1. An approved simulation suite produced in Generation / Setup Wizard
  2. At least one assurance result with score + evidence
  3. That result visible in History

Get started — the Studio loop

Map of the QAVE Studio assurance loop — Setup Wizard through Assurance Lab, with deep links to every guide.

First assurance run

End-to-end path from context template to History using the reference SUT.

On this page

Choose your pathPrerequisitesWhat “done” looks like