Start a sandbox
Starts a sandbox on one of the team’s connected sandbox accounts that CostGraph can run. With no provider, CostGraph AutoPilot orders the connected providers for the size and policy, as the route endpoint does, and when a provider cannot start the sandbox the next one is tried; every failed attempt is recorded. provider limits the start to that connected provider. Send the size as size_class (xs, sm, md, lg, xl or 2xl), or as vcpus and memory_mib; with neither, each provider starts its own default size. policy (cheapest, balanced or fastest) overrides the team’s policy for this sandbox. metadata holds at most 16 string tags, which are passed to the provider as labels, and metadata.run, the run key, also sets the provider’s run label, and a new run key is generated when it is absent; keys starting with costgraph.ai/ are reserved and dropped. lifecycle.timeout_ms asks the provider to end the sandbox after that many milliseconds. The sandbox is recorded as started with its price per hour, so it shows in the sandbox list and in AutoPilot savings. routed_from names the provider tried first when the sandbox started elsewhere. When every provider tried refuses the sandbox, for its size, credits, plan or key, nothing was started and the answer is 422 with what to change; 502 means a provider may still have started one.
Body
Provider, size, policy and tags