---

Short, self-contained code you copy, run, and adapt — not reference documentation. For API references and guides, see the Reactor docs.

Structure

The three top-level folders cover distinct ways to build with Reactor.

• examples/ holds complete applications and demos built on hosted Reactor models. Each example is a top-level, self-contained project you can copy, run, and adapt. The per-model reference frontends — one for each model Reactor serves on the API, and the templates npx create-reactor-app scaffolds from — live beside that CLI in reactor-team/create-reactor-app.
• models/ holds models you deploy. Each folder is a reactor workspace you build and run with the CLI, and everything that deployment needs lives inside it. Build your own model covers the workspace they follow.
• robotics/ holds code that drives a model someone else is already serving: policy quickstarts and closed-loop simulator integrations built on the Python SDK.

Each example has a README explaining what it does and how to run it.

Contributing

Adding a complete application or demo? Put it directly under examples/. Put model deployments under models/ and robotics integrations under robotics/. Keep each project self-contained, give the folder a name describing what it does rather than the API it happens to call, and lead its README with the problem it solves. Model deployments follow the rules in GUIDELINES.md.

License

Apache-2.0 — see LICENSE.