Agent1

Agent browsers7

Catalog13

Chat sessions10

Clients7

Conformance runs9

Directory readiness6

Environments12

Eval runs45

Eval suites2

Evals4

Execution3

Export1

Harness1

OAuth1

Plugins2

Primitives7

Projects4

Registry8

Sandbox images11

Secrets5

Server connections4

Server diagnostics3

Servers4

Skills2

Studies21

Swarm insights8

Swarm runs5

Swarms17

Tunnels2

Studies

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}/studies/{studyId}/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.