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
Execute & Traces

Recipe chatbot (reference SUT)

Use the recipe-chatbot HTTP API as the canonical system under test for tutorials.

The recipe-chatbot is the reference system under test for QAVE Studio tutorials. It is a conversational FastAPI app with optional Langfuse tracing.

Endpoints

MethodPathPurpose
POST/api/chatPrimary SUT surface
GET/healthReadiness
GET/Chat UI

Chat contract

// Request
{ "session_id": "optional", "message": "..." }
// or OpenAI-style messages[]

// Response
{ "session_id": "...", "reply": "...", "model": "..." }

Optional header: X-Session-Id.

Local ports

Compose often maps the app to 9000; avoid colliding with the Gateway on 8000.

curl -s http://localhost:9000/api/chat \
  -H 'Content-Type: application/json' \
  -d '{"message":"Give me a quick weeknight dinner idea"}'

Tracing

When LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY are set, chat emits Langfuse traces (for example recipe-chatbot-session). Local JSON traces also land under the app's data/traces.json.

MCP

MCP evaluate_conversation on the chatbot is not implemented. Do not point the SDK agent at {chatbot}/mcp expecting a real score path — use HTTP chat + Langfuse/paste instead, or the mock MCP for agent demos.

Execute and traces

Drive the system under test and capture traces for assurance.

Tracing

Capture correlated traces from the SUT for later assurance.

On this page

EndpointsChat contractLocal portsTracingMCP