peaq_ros2_peaqos maps the peaqOS Python capability surface into typed ROS 2 services. It is for robot teams that already run ROS 2 and want peaqOS primitives without passing through ROS messages. ROS 2 stays the robot control plane; peaqOS becomes the machine economy and identity plane.
The services wrap the Python SDK’s register_machine, register_for, mint_nft, and DID-attribute calls, which onboard machines on the Tokenomics 1.0 contracts. Economics 2.0 activation (activate_machine) has no ROS 2 service. See Activate.
What it does
Machine onboarding
Create local EVM machine wallets, register machines, and fund them through the Gas Station.
Machine identity
Mint Machine NFTs and write the standard DID attributes.
Machine telemetry
Validate single events locally, submit one event, or batch-submit atomically through the peaq batch precompile.
Machine accounts
Preview and deploy deterministic ERC-4337 smart accounts through
MachineAccountFactory.Cross-chain assets
Bridge Machine NFTs between peaq and Base via LayerZero V2.
Security model
- private keys live in one local registry file on the robot or machine (default
~/.peaq_robot/peaqos_wallets.json, perms0600). - ROS callers pass EVM addresses, not private keys.
- The node never accepts or returns private keys over ROS.
- Wallet
list/get/deleteexpose only public metadata:address,account_id,chain_id,network,label,created_at. - Faucet 2FA codes are used for a single request. Do not log them.
Service map
The node also registers
mcr/query, mcr/machine and mcr/operator_machines. They do not work with the MCR API, which covers Economics 2.0 machines only. Query MCR with the Python SDK or the MCR API instead.
Full service-by-service reference with example payloads is on Services. Bridge has its own page on Bridge. A Base to peaq call needs Base ETH on the wallet for .
Quickstart
Build and source the workspace, copy the example config, then start the node against your unified config:ROS distro support
Native install on non-Linux hosts is best done via Docker or WSL.
Keep going
Configuration
YAML fields, contract addresses, wallet registry, API URLs, and environment overrides.
Service catalog
Canonical machine endpoints plus documented agent aliases, with request fields and examples.
Stream Edge Agent
Sign, encrypt, and sell machine data from a ROS 2 node, the on-machine half of Stream.
ROS 2 guide
Run the Tokenomics 1.0 onboarding, event, smart-account, and bridge flow from ROS 2.
peaqOS Python SDK
The PyPI SDK surface wrapped by the ROS 2 node.
peaqOS JavaScript SDK
The JavaScript SDK surface used for peaqOS application integrations.

