Use the robot's APIs¶
Everything the platform does is reachable as an API — and the panel's APIs tab hands you every command ready to run.
The APIs tab¶
- Open the PhysiCar panel → APIs.
- Cards are grouped by target (Robot / Simulator) and transport (Web / ROS 2).
- Every card has a play button — it runs the command right in the panel — and a copy button for the terminal.
Works signed-out; it is the fastest way to discover what the robot can do.
The robot's web API¶
The robot serves a web API on its own address — drive, camera, sensors, racing
runner. Explore the cards, then call the same endpoints from your own code
(requests in Python, fetch in a web app). Your MyApp
talks to the robot exactly this way.
ROS 2 topics¶
For continuous control and sensor streams, use ROS 2 directly:
ros2 topic list
ros2 topic echo /scan --once
ros2 topic pub /speed std_msgs/msg/Float64 "{data: 0.3}" -1
The full topic contract (names, types, ranges) is in the physicar-ros reference.
New to ROS 2? → Learn: ROS 2 overview