B2B Fleet Onboarding Guide
Step-by-step guide to set up AI Teammate for your robot fleet.
1B2B Account Signup
Create your company account and get fleet access
2Create Robot Agent
Build an AI agent with robot control skills to unlock Control Tower
3Install Bridge on Robot
One command — no manual key generation needed
4Verify & Manage
Check bridge status and manage sensors
5Assign Device to Fleet Project
Link robots to your fleet for monitoring and broadcast
6Control Tower
SLAM, joystick, camera, sensors — all in one dashboard
7Fleet Operations
Emergency stop, session collaboration, auto-updates
Overview
Time to Setup
~15 minutes
Requirements
Ubuntu + ROS2 Humble/Jazzy
Support
support@mobiolabs.net
1
B2B Account Signup
Go to [/b2b/signup](https://ai-teammate.net/b2b/signup) and fill in:
- Company name & contact info
- Admin account (email + password)
After signup, a **Fleet Project** is auto-created for your company.
Your admin account has fleet_enabled — access to Control Tower.
2
Create Robot Agent
Create an agent with robot control skills — this is required to access Control Tower:
1. Go to Create Agent (or use "ROS2 Fleet Manager" template)
2. Enable skill: ext_device_gateway or ext_ros2_robot
3. Use a robot system prompt (templates available)
4. Save — a **Control Tower icon** (cyan) appears on the agent card
The agent's chat memory is shared with Control Tower, so all robot commands and responses are stored in the agent's conversation history.
3
Install Bridge on Robot
Go to Control Tower > **Setup** tab — copy the install command (your JWT is pre-filled):
curl -sL ".../install/MY_ROBOT_01/preflight?token=YOUR_JWT" | bash -s -- --install --yes
- **Device ID** is created automatically on first install
- **API key** is auto-provisioned (no manual generation)
- **Owner** is bound to your account via the JWT token
You can also pre-register a device in **Devices tab > + Add Device** if you want to assign a name before install, but it's optional.
4
Verify & Manage
After install completes ("✅ Robot ... is ONLINE"):
Verify:
tail -f ~/ai-teammate-bridge/bridge.log
Useful commands:
- Restart: systemctl --user restart ai-teammate-bridge
- Update: pip3 install --upgrade ai-teammate-ros2-bridge
- Regenerate sensors: FORCE_SENSORS_YAML=1 curl ... | bash
**Sensor config:** ~/ai-teammate-bridge/sensors.yaml — auto-generated from detected topics. Edit freely; reinstall won't overwrite unless FORCE_SENSORS_YAML=1.
The robot should appear in **Control Tower > Devices** tab as "connected" within seconds.
5
Assign Device to Fleet Project
In Control Tower > Devices tab:
- Find your registered device
- Assign it to your Fleet Project
This enables:
- Fleet status summary (online/offline, battery)
- Fleet broadcast commands (emergency stop all)
- Session-based multi-robot collaboration
6
Control Tower
Access from the agent card (cyan radio icon) or directly at /control-tower:
Tabs:
- **Status** — Device health, quick actions
- **Fleet** — Real-time fleet overview, Emergency Stop All
- **SLAM** — Live mapping + joystick control
- **Camera** — Live video stream
- **Sensors** — IMU, odometry, battery charts
- **Nav2** — Path planning & navigation goals
7
Fleet Operations
**Broadcast Stop:** Fleet tab > Emergency Stop All — stops every robot in the fleet via MQTT.
Session Collaboration:
- Create a session in Fleet tab
- Connect multiple devices to the same session
- Broadcast commands to all devices in session
**Auto-Update:** Bridge checks for updates hourly and self-upgrades.