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.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Scenario ID, as returned by publishing an environment or by the project's scenario reads.
Body
The spend dial for ANONYMOUS visitors. Replaced as a whole, never patched: these caps only mean something as a set, and a partial update that raised dailyCreditCap while leaving a stale maxConcurrentComputers behind would produce a combination nobody chose.
Master switch. Everything below is inert while this is false.
Hard ceiling on what visitors can spend per day, in credits.
x >= 0x >= 0x >= 0Integer USD micros.
x >= 0x >= 0x >= 0Response
The caps now in force.
The spend dial for ANONYMOUS visitors. Replaced as a whole, never patched: these caps only mean something as a set, and a partial update that raised dailyCreditCap while leaving a stale maxConcurrentComputers behind would produce a combination nobody chose.
Master switch. Everything below is inert while this is false.
Hard ceiling on what visitors can spend per day, in credits.
x >= 0x >= 0x >= 0Integer USD micros.
x >= 0x >= 0x >= 0
