Run Evaluator Websocket
Execute evaluators where each scenario carries its own websocket URL. Useful when you have a fleet of agents or stateful websocket sessions to test in a single batch.
Authorizations
OAuth access token issued by Cekura for connected apps.
Body
List of scenario+websocket pairs. Each element must be an object with two keys: scenario (integer evaluator ID) and websocket_url (string, ws:// or wss:// URL). Example: [{"scenario": 101, "websocket_url": "wss://agent-a.example.com/chat"}, {"scenario": 102, "websocket_url": "wss://agent-b.example.com/chat"}]
Frequency to run
1 <= x <= 100Agent to use. Required if none of the scenarios have an agent.
Names of mock tools to activate for this run. Omit (or send null) to mock every tool configured on the agent; send an empty list to mock none so every tool keeps its original endpoint; send specific names to mock only those. Tools that belong to an MCP server should be selected via the MCP server's name or key, which mocks all of that server's tools as one unit. Legacy MCP sub-tool names are accepted as aliases for the whole parent MCP.
Response
ID of the result
ID of the agent
Status of the result
pending, running, completed, failed Whether the scenario ran as text or not
false
"2025-02-25T21:00:01.990052Z"