Skip to main content
A World starts named Simulations together and returns their service endpoints. Use a World when an agent needs several systems in one environment.

​
Define the members

Map each service name to a ready Simulator reference. Continuous derives a stable member seed from the World seed and member name.
The result includes one endpoint for each named member. Member Simulations keep separate state while the World coordinates their lifecycle.

​
Control the World

Stop or start every member through the World.
Clone a World to reuse its pinned Simulator revisions with fresh member Simulations.
Use the API reference for exact World routes and schemas.

Understand Simulators

Learn what each World member runs.

Understand Simulations

Learn how each member owns state and time.