The InOrbit Agent is the recommended way to connect ROS and ROS 2 robots to InOrbit. It runs directly on your robot, providing:Documentation Index
Fetch the complete documentation index at: https://inorbitinc.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- Native ROS integration — Automatic discovery of topics, maps, and cameras
- Secure communication — Encrypted, optimized data channel to InOrbit cloud
- Adaptive sampling — Smart throttling to minimize bandwidth
- Offline buffering — Data is queued when connectivity is lost
- Scripted actions — Execute commands on your robot from InOrbit
- Video streaming — Stream camera feeds to InOrbit Control
Quick Start
1. Get Your Account Key
Log in to InOrbit Console and navigate to Add Robot. Copy your account key.2. Install the Agent
Run this one-line command on your robot (replaceYOUR_ACCOUNT_KEY):
By default, the robot name is its hostname. You can change this during installation or later in InOrbit Console.
3. Verify Connection
Check that the agent is running:"InOrbit Agent API: OK"
Installation Options
Debian Package
For production deployments, install the agent as a Debian package:Agent Core Only
If you’re using the Robot SDK and only need the core agent (without ROS integration):ROS Integration
The agent automatically detects and subscribes to common ROS topics. You can customize which topics are mapped to InOrbit from InOrbit Console under robot settings.Publishing Custom Data
You can publish custom key-value data to InOrbit via ROS topics:Configuration
Agent configuration is stored in~/.inorbit/local/. Key files:
| File | Purpose |
|---|---|
agent.env.sh | Environment variables (API port, binding address) |
inorbit_agent.log | Agent logs |
Common Configuration
Edit~/.inorbit/local/agent.env.sh to customize:
Troubleshooting
Next Steps
Robot SDK
Add custom data with C++ or Python
Configure Data Sources
Define what data to collect