1
Install
- CLI
- npm
- pip
- Agent skill
peaqos init writes a .env with your key, RPC, and PEAQOS_DEPLOYMENT_ID (peaq-mainnet, or agung-2026-08-28 for the testnet). Needs Python 3.10 or newer. Full reference on the peaqOS CLI page.2
Configure
Create a
.env file, or let peaqos init write it. This is what peaqos init writes for peaq mainnet:PEAQOS_DEPLOYMENT_ID=agung-2026-08-28 selects the testnet record; unset means peaq-mainnet. Other public RPC endpoints are on the install page. PEAQOS_GAS_STATION_URL is needed for the peaqos activate funding step; drop it and pass --skip-funding if the wallet already has gas. The SDKs’ fromEnv() / from_env() read PEAQOS_RPC_URL and PEAQOS_PRIVATE_KEY (required), plus PEAQOS_DEPLOYMENT_ID, PEAQOS_SVM_RPC_URL (non-empty enables Solana reads) and PEAQOS_ORCHESTRATION_URL; their API key variable is PEAQOS_API_KEY, not the CLI’s PEAQOS_ORCH_API_KEY, so set both to the same value if you use both.The wallet behind PEAQOS_PRIVATE_KEY becomes the machine’s owner and pays the plus . The bond is quoted per tier at the oracle rate and the PEAQ figure moves with the daily oracle price, so preview before you fund. See Economics 2.0. Full variable list on the environment variables table.3
Activate
- CLI
- JavaScript
- Python
Sensor, 0xdeadbeef and the z6Mk... key with your machine’s own values before you submit. The machine type and credential subject fix the machine ID for good: everyone who copies the sample values gets the same ID, and only the first activation succeeds. Nothing checks the key value, so a placeholder is stored as given.For the full terminal walkthrough, wallets and costs included, follow the onboarding quickstart. Fleets activate each machine with the machine’s own key and record the operator as DID controller. See the self-managed and fleet guides.What just happened
What just happened
- The client resolved the Economics 2.0 contract addresses from the
peaq-mainnetdeployment record and verified them againstInfoDesk.peer(role)on chain. activateMachinesent one transaction that minted the machine’s ERC-721 inMachineRegistry, stored the DID document, bonded PEAQ on the Entry tier inMachineSubscription, and recorded peaq as the home chain.- The is
uint256(keccak256(abi.encode(machineType, credentialSubject))). It is also the NFT token ID and the DID isdid:peaq:<that id>. It is the handle for every later call:peaqos machine status, renewals, transfers, DID updates. - The SDK only returned after the receipt carried
MachineOnboarded,MachineMinted, andActivatedand the on-chain state matched what you asked for. - The machine shows up on the Machine Explorer at
machines.peaq.xyz/machine/<decimal machine id>once the indexer has picked up the block.
Next
Onboarding quickstart
From a blank terminal to an activated machine on peaq, with the CLI.
Self-managed onboarding
Owner = operator. One machine, one wallet, funded through the Gas Station.
Fleet onboarding
Many machines, each owning its NFT, one operator as controller.
Scale: pair an agent, buy services
Pair an AI agent to your machine and let it discover and consume services through the Machine Markets API. Paused: Machine Markets is not open to new partners yet; it accepts bonded machines homed on peaq or Solana, with an EVM or Solana DID controller.

