Overview
Use this flow to test your agent by joining a Pipecat session via WebRTC for each evaluator run. Each item you submit will create a run that connects using your provided Pipecat session URL and configuration.Each array element you send creates a separate run. To run the same scenario multiple times in parallel, repeat that scenario object multiple times in the payload.
Prerequisites
- A Cekura account
- One or more scenarios created for your agent
- Pipecat agent endpoint and any required authentication tokens for each run you intend to start
API Endpoint
- Method: POST
- URL:
https://api.cekura.ai/test_framework/v1/scenarios-external/run_scenarios_pipecat/ - Headers:
X-CEKURA-API-KEY: your API keyContent-Type:application/json
Request Body
- scenarios: Array of objects. Each object fields:
- scenario (number, required): Scenario ID
- pipecat_room_url (string, required): Pipecat WebRTC room URL to connect to
- pipecat_token (string, optional): Authentication token for the Pipecat room
- publish_data_message (object, optional): JSON data message to publish during the session
Example: Minimal Single Run (cURL)
Example: Multiple Runs (JSON)
Example: Python
Expected Behavior
- A result is created and a run is queued for each item in
scenarios - Each run connects to the provided Pipecat WebRTC room using the given token
- You can poll run statuses using the Bulk Runs API:
API Reference
Get Runs with IDs: API Doc
Troubleshooting
- 401/403 errors: Check your
X-CEKURA-API-KEY - Connection failures: Verify
pipecat_room_urlandpipecat_tokenare correct - No runs created: Ensure the
scenariosarray is not empty and scenario IDs are valid - WebRTC connection issues: Ensure the Pipecat room URL is accessible and the token is valid for the session
Next Steps
- Learn about custom metrics
- Explore predefined metrics
- Set up instruction following metric
- Perform load testing