Skip to main content
Run agent quality simulations, manage test datasets, and validate agent behavior through the API. Also available as MCP tools for AI agent workflows.

Authentication

All endpoints require an API key with agents_config:read or agents_config:write scope.

Quick Test

Run a single ad-hoc test against an agent. Returns the response synchronously (may take 10-30 seconds).
Response:
Scope: agents_config:write

Datasets

Datasets group related test cases for batch simulation runs.

List Datasets

Response:
Scope: agents_config:read

Create Dataset

Scope: agents_config:write

Get, Update, Delete Dataset

Deleting a dataset removes all its test cases and runs.

Test Cases

Each test case defines a question and the expected agent behavior.

Expected Types

Create Test Case

Answer test:
Tool call test:
Multi-turn test (conversation with multiple exchanges):
Steps run in sequence within the same conversation thread, so the agent retains context. Scope: agents_config:write

List Test Cases

Scope: agents_config:read

Bulk Create

Import from Conversation

Extract a test case from an existing conversation thread:
Uses the last user message and assistant response from the thread. Scope: agents_config:write

Personas

Personas simulate different user profiles during testing. They can override the agent, LLM temperature, available tools, and user attributes.

Create Persona

Scope: agents_config:write

List, Get, Update, Delete Personas


Simulation Runs

Start a Run

Runs execute asynchronously. The response returns immediately with status: "pending". Scope: agents_config:write

Poll Run Status

Poll this endpoint until status is "completed" or "failed". Scope: agents_config:read

Get Run Details

Get Run Results

List Runs, Delete Run


MCP Tools

All simulation endpoints are available as MCP tools. Connect to the MCP server at /api/v1/mcp with an API key that has agents_config scopes.

Workflow: Run a Simulation via MCP

  1. Start the run: Call start_simulation_run with dataset_id and agent_id
  2. Poll for completion: Call get_simulation_run_status with run_id until status is "completed" or "failed"
  3. Get results: Call get_simulation_run_results with run_id to see individual test results

Available MCP Tools


Error Responses

Errors follow the standard API v1 format: