latestOpenAPI 3.1.0raw.githubusercontent.com2026-08-15140179507.6 KB

d3adfe49fbbf

User testing

Set the guest-execution caps

The spend dial for anonymous visitors. A FULL REPLACEMENT — send every field. These caps only mean something as a set, and a partial update that raised one while leaving another stale would produce a combination nobody chose.

Requires project ADMIN: it is the one exposure control that genuinely does, because it authorizes strangers to spend.

put/projects/{projectId}/user-testing/scenarios/{scenarioId}/guest-execution

Request body

enabledboolean required

Master switch. Everything below is inert while this is false.

computerEnabledboolean required

sharedSkillsEnabledboolean required

dailyCreditCapnumber required

Hard ceiling on what visitors can spend per day, in credits.

dailyComputerStartCapinteger required

maxConcurrentComputersinteger required

harnessEnabledboolean

dailyHarnessSpendCapMicrosinteger

Integer USD micros.

dailyHarnessCallCapinteger

maxConcurrentHarnessRunsinteger

Response

The caps now in force.