> ## Documentation Index > Fetch the complete documentation index at: https://docs.usefini.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Create Test Suite regression sets, attach criteria, start runs, and read run results through Fini's public API. Test sets are the API form of the dashboard [Test Suite](/en/testing/test-suite). A test set groups existing conversations, attaches one or more grading criteria, and queues asynchronous runs that evaluate those conversations against the current agent behavior. Use these routes when you want to seed regression checks from conversations already in Fini, manage their criteria from your backend, or trigger a run after changing prompts, knowledge, rules, or actions. Test set runs evaluate existing conversation IDs. Create or import the conversations first, then pass their IDs in `conversationIds` when you create or update a test set. ## Endpoints Return every test set in the workspace, newest first. Create a set from one to 200 existing conversation IDs. Read default criteria and deterministic-condition fields. Fetch a test set with its resolved criteria. Update the set name, description, or conversation list. Delete a set after active runs finish. Attach default or custom criteria to a set. Change one criterion on a set. Remove one criterion from a set. Page through run summaries for one set. Queue an asynchronous evaluation run. Fetch one run and its detailed result. ## Authentication Bearer token containing your Fini workspace API key. Format: `Bearer fini_...` Write routes also require `Content-Type: application/json` when they send a body. ## TestSet object Test set ID. Workspace ID that owns the test set. This field is omitted from list summaries. Test set name. Optional description. Existing Fini conversation IDs included in the set. The API accepts 1 to 200 UUIDs. User ID that created the set. API-created records can be `null`. ISO 8601 creation timestamp. ISO 8601 last-update timestamp. List responses return `conversationCount` and `criteriaCount` instead of the full `conversationIds` array. ## Criterion object Criterion ID. Test set that owns the criterion. Default criteria return `null`. Workspace that owns the criterion. Fini-provided defaults can return `null`. Default criterion copied into this test set, if this criterion was created from a default. Criterion label. One of `deterministic`, `basic_judge`, or `complex_judge`. Judge prompt for LLM-graded criteria. What should count as a pass for LLM-graded criteria. What should count as a fail for LLM-graded criteria. Deterministic condition. Allowed root paths are `knowledgeSearchUsed`, `usedArticles`, `usedKnowledgeFolders`, `intentRules`, `tagGroups`, and `replyTypes`. Whether failing this criterion should make the conversation fail overall. Whether the criterion is active. ## Run object Test run ID. Test set evaluated by the run. `running`, `completed`, or `failed`. Full result for [Get a run](/en/api-reference/get-test-set-run). While the run is queued or processing, this is `null`. User ID that started the run. API-started runs can be `null`. ### Result shape When a run completes, `result.summary` contains aggregate counts and `result.conversations` contains per-conversation results. Overall verdict, `pass` or `fail`. Number of conversations evaluated. Conversations with a passing result. Conversations with a failing result. Conversations that errored during evaluation. Criterion-level verdicts, reasoning, and evidence for each evaluated conversation. ## Errors The request body or query parameters failed validation. Common cases: empty names, invalid UUIDs, more than 200 conversation IDs, no criteria before starting a run, or invalid criterion definitions. The API key is missing, malformed, revoked, or invalid. The API key does not include the required `read` or `write` scope. The test set, criterion, run, default criterion, or conversation does not exist in your workspace. The test set has an active run and cannot be deleted until the run finishes.