Skip to content

Sandboxes · 18 November 2026

A key can hold only the actions its code calls, on every plan

POST /v2/keys takes actions, such as ["sandboxes:create", "sandboxes:exec", "sandboxes:get"]: the key acts as an agent of its own, granted a role of exactly those actions, and each must be one its maker may do where the key acts. Give a worker a key that cannot delete, and a dashboard a key that only reads. It holds its maker's limits too (spend cap, rate, allowed addresses, end), acts in every project its maker reaches (a key held to one project starts at Growth), and a key made with it holds the same actions. Deleting the key deletes its role at once and its agent with its row. Keys made by 1.0's POST /v1/keys, each with an agent of its own, now take that agent with them too, and no other key can be made to act as it. See API keys and access.

Same day.

Cut your cloud billby 74%.

Redeem $5 free usage$0 today · 7 days free · cancel any time

7 days of Pro for $0, and no card to sign up. Billed by the second after.

Redeem $5 free usage$0 today · 7 days free · cancel any time