Skip to main content
POST
Estimate a run
Estimates a run for a LIVE workspace. It does not reserve or spend credits and requires no Idempotency-Key. The endpoint still requires a write-enabled plan and consumes the write rate-limit budget. Requires an active Business, Agency Business or Enterprise plan. Use an API token with write access enabled. See Writing data for idempotency, conditional requests and error handling.
string
required
Bearer token for your team.
string
required
Workspace identifier. The workspace must belong to the token’s team.
string[]
Up to 50 active prompt UUIDs. Omit to select all active prompts. If that would exceed 50, explicitly select a smaller set.
string[]
Up to 20 Qwairy model codes. Omit or send [] to use the workspace’s selected monitoring models.

Response

Returns 200 with estimate. When every requested model is excluded, the response is still 200, with zero counts and credits and the excluded codes in unsupportedModels: An estimate is a snapshot. Starting the run revalidates targets and reserves credits; its result can differ if availability or balance changes.

Synthetic request and response

Errors

Invalid or oversized targets return 400 INVALID_REQUEST; inaccessible resources return 404 RESOURCE_NOT_FOUND. A non-live workspace, an empty prompt selection, or no usable model returns 409 CONFLICT. See Error codes for authentication, plan, idempotency and server errors. On 429, honor Retry-After; writes can return 503 SERVICE_UNAVAILABLE if the write limiter is unavailable.