API-first robotics
If you want to treat Cyberwave as an API-first control plane (an “AWS for robotics”), you can integrate directly through our public APIs and build your own UI, orchestrators, and data pipelines.
What you get with the APIs
A stable control plane + real-time data plane you can plug into any product.
Control plane primitives
Create and manage assets, twins, environments, access control, workflows, datasets, and training runs via REST.
Real-time streams
Use MQTT for low-latency telemetry + command channels without polling.
Auth & governance
Tokens, org/workspace boundaries, and permissioned operations designed for multi-tenant deployments.
Digital twin lifecycle
Instantiate twins from catalog assets, update state/joints, attach telemetry, and keep runs traceable.
Two main APIs
Cyberwave exposes two primary integration surfaces:
- REST API: non-real-time operations like creating/managing twins, assets, permissions, workflows, datasets, and training runs.
- MQTT API: real-time command/telemetry and low-latency event streams.
References
Go straight to the API reference
Everything you need to treat Cyberwave as an API product: endpoints, schemas, and MQTT topics.