---
title: "Set the guest-execution caps"
method: PUT
path: "/projects/{projectId}/user-testing/scenarios/{scenarioId}/guest-execution"
tags: ["User testing"]
---

# Set the guest-execution caps

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

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.

## Request body

- GuestExecution — 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.
  - `enabled` boolean, required — Master switch. Everything below is inert while this is false.
  - `computerEnabled` boolean, required
  - `sharedSkillsEnabled` boolean, required
  - `dailyCreditCap` number, required — Hard ceiling on what visitors can spend per day, in credits.
  - `dailyComputerStartCap` integer, required
  - `maxConcurrentComputers` integer, required
  - `harnessEnabled` boolean
  - `dailyHarnessSpendCapMicros` integer — Integer USD micros.
  - `dailyHarnessCallCap` integer
  - `maxConcurrentHarnessRuns` integer

## Response `200`

The caps now in force.

- GuestExecution — 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.
  - `enabled` boolean, required — Master switch. Everything below is inert while this is false.
  - `computerEnabled` boolean, required
  - `sharedSkillsEnabled` boolean, required
  - `dailyCreditCap` number, required — Hard ceiling on what visitors can spend per day, in credits.
  - `dailyComputerStartCap` integer, required
  - `maxConcurrentComputers` integer, required
  - `harnessEnabled` boolean
  - `dailyHarnessSpendCapMicros` integer — Integer USD micros.
  - `dailyHarnessCallCap` integer
  - `maxConcurrentHarnessRuns` integer

## Other responses

- `400` — Malformed body or parameters.
- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/7d1aff84ce3b/schema)