> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peaq.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Enterprise-grade ROS 2 integration for the peaq robotics stack.

The peaq Robotics SDK for ROS 2 brings blockchain-native identity, access, and storage flows to ROS applications. It exposes simple modules you can use across robot fleets:

* [Identity (`id`)](/peaqchain/sdk-reference/robotics-sdk/ros2/core-services/identity): create and read identity documents
* [Access (`access`)](/peaqchain/sdk-reference/robotics-sdk/ros2/core-services/access): roles, permissions, and grants
* [Storage (`store`)](/peaqchain/sdk-reference/robotics-sdk/ros2/core-services/storage): write and read compact JSON data
* [Tether WDK (`tether`)](/peaqchain/sdk-reference/robotics-sdk/ros2/tether/overview): create EVM addresses, read USDT balances, and transfer USDT on peaq EVM

Coming soon:

* Verification
* Time

> Note: The current ROS 2 integration targets Humble (or later) and works on the same robot classes as the Robotics Python SDK—from Unitree models to TurtleBot/HiWonder—whenever ROS 2 is available on the device.

Quickstart:

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark"}}
# Clone and build
git clone https://github.com/peaqnetwork/peaq-robotics-ros2.git
cd peaq-robotics-ros2
pip install -r requirements.txt
source /opt/ros/humble/setup.bash
colcon build && source install/setup.bash

# Launch core services
ros2 launch peaq_ros2_core core.launch.py

# Configure and activate lifecycle
ros2 lifecycle set /peaq_core_node configure
ros2 lifecycle set /peaq_core_node activate

# Create an identity
ros2 service call /peaq_core_node/identity/create \
  peaq_ros2_interfaces/srv/IdentityCreate \
  '{metadata_json: "{\"type\": \"robot\"}"}'
```

What you’ll learn here:

* Installation and environment setup
* Configuration and launching core services
* Reading/writing identity and storage data
* Access control (roles, permissions, grants)
* Event streams and verifiable storage pipelines
* End‑to‑end runnable examples