Start with peaqOS
The opinionated Machine Financial Passport flow. What 95% of teams should use.
Build at the protocol layer
Solidity, node operations, staking, and the legacy peaq SDK primitives.
When to use peaqOS vs peaq chain
| I want to… | Use |
|---|---|
| Give a machine a cross-chain identity | peaqOS Activate |
| Query a machine’s credit rating from another chain | peaqOS MCR API |
| Submit revenue events for a fleet | peaqOS SDK (proxy operator) |
| Delegate spending to an AI agent | peaqOS Scale |
| Deploy a Solidity contract | peaq chain (Build tab) |
| Run a validator | peaq chain (Node operations) |
| Write to the DID pallet directly | peaq SDK (legacy) |
| Use on-chain RBAC primitives | peaq SDK (legacy) |
| Fractionalize a machine as an RWA | peaqOS Tokenize + peaq chain RWA SDK |
Both SDKs coexist.
@peaqos/peaq-os-sdk is the opinionated path through the Machine Financial Passport flow. @peaq-network/sdk gives full access to peaq chain primitives (DID pallet operations, RBAC, Storage, UMT, chain-level transactions). Most teams use peaqOS SDK; drop to peaq SDK for primitives peaqOS does not cover.What you’ll find in this section
- Build reference: Solidity deployments, gas, wallets, event listening, indexers, precompiles, node operations, account abstraction, and ERC-8004 at the contract layer.
- SDK reference: legacy
@peaq-network/sdk(JavaScript + Python), the Robotics SDK (Python + ROS 2), and the RWA SDK for fractional ownership primitives. - Tokenomics: $PEAQ supply, inflation schedule, validator rewards, and staking economics.