Create a demo cloud simulation from a list of resources and connections (max 2 per session, up to 10 resources; demo simulations are temporary and are cleaned up after roughly 30 minutes or when the session ends). If you don't have an architecture in mind, call `scenario.list` first — its `resources` and `connections` arrays can be passed directly here. Use it to start any simulation workflow — either with resources from scenario.list or your own architecture. Do not use it to modify an existing simulation (use simulation.inject_traffic to change load). To give a resource an explicit capacity, set characteristics.capacityRps — the literal per-node RPS ceiling at which CPU reaches ~95%; do not use maxThroughput for this (it is a legacy internal scaling parameter with different semantics). To bound the autoscaled fleet size, set the top-level maxInstances / minInstances parameters. If you do not set maxInstances, the engine uses the provider default — AWS 50, GCP 15, Azure/OCI/DigitalOcean 10 — which may be much larger than your intended fleet size. The response includes effectiveMaxInstances / effectiveMinInstances so you can confirm the bounds that will be enforced. Responses are compact by default: id, name, status, traffic, and a per-resource summary (id, name, status, cpuPercent). Pass responseMode: 'full' to get the complete simulation object instead. No prerequisites. Returns the created simulation's id, which every other simulation.* tool consumes; the new simulation also becomes this session's current simulation, so subsequent per-simulation tools may omit simulationId. The likely next tool is simulation.step to advance time. Do not call api.spec to learn the simulation workflow — the tool descriptions in this session contain everything needed. Authenticate with an API key for unlimited persistent simulations.
Connector