Skip to main content
peaq turns robots, vehicles, sensors, AI agents, and other machines into economic participants: machines that earn, transact, build reputation, access capital, and become investable assets.

​
What peaq provides

Identity

Give machines a verifiable identity that works across chains.

Reputation

Track performance, reliability, and activity as a portable .

Payments

Enable autonomous transactions, including agent-delegated spending.

Machine earnings

Let machines sell their spare capacity and earn to their own wallet.

Ownership

Tokenize and invest in machines and machine networks.

Services

Let machines buy and sell data, AI, compute, storage, and other services.
Under the hood, peaq combines these machine economy services with a trust infrastructure that records ownership, reputation, transactions, and economic activity in a verifiable way.

​
Architecture

peaqOS

The machine economy operating system that developers and machines interact with. Identity, credit and payments through one SDK, with tokenization next. Most teams build here and never go deeper.

peaq Trust Layer

The decentralized infrastructure layer that secures ownership, reputation, payments, and coordination across the machine economy. is the ; state mirrors out to so machines can transact wherever their counterparties are.
peaqOS runs on the Trust Layer and abstracts it. Identity and credit records live in peaqOS contracts on the home chain, mirror out to satellite chains, and any chain can read them through the API. You drop down to the Trust Layer directly only when you need something peaqOS does not already cover. An Economics 2.0 machine can also be homed on Solana: its identity, DID document and Machine NFT live on Solana, and its bond is paid on Solana and booked on peaq (Solana onboarding).

​
Start building

Activate your first machine

The five-minute peaqOS flow. Install the SDK, activate a machine in one transaction, manage it.

Build on the Trust Layer

Solidity, node operations, staking, and the peaq chain SDK primitives.

​
When to use which

Most of the time the answer is peaqOS. Drop to the Trust Layer (peaq chain) when you need protocol-level control. There are two SDKs. @peaqos/peaq-os-sdk is the opinionated path through the machine flow. @peaq-network/sdk gives raw access to peaq chain primitives (DID, RBAC, storage, UMT, chain transactions). Most teams use peaqOS and never touch the chain SDK directly.

​
Who it’s for

Builders

Give your machines identity, credit, and financial infrastructure. Start with the onboarding quickstart.

Operators

Activate a whole fleet. Every machine owns its NFT; one operator controls them all.

Capital allocators

Query an Economics 2.0 machine’s credit rating from any chain with one API call.

​
Keep going

Roadmap

What ships when.

Glossary

Plain-English web3 terms.

GitHub

Source and SDKs.

Discord

Builders, operators, OEMs.