Activate - peaq

Activate is the entry point to peaqOS. on and give it a peaqID, a , and a Machine NFT: the primitives every later function builds on.

What ships

Component	Description
peaqID	W3C DID anchoring the machine’s on-chain identity. Portable across chains.
Identity NFT	Minted automatically by IdentityRegistry at registration. `tokenId == machineId`.
Machine NFT	LayerZero V2 ONFT linking to the machine’s financial profile. Minted via a separate `mintNft` call after registration. See Machine NFT ownership.
1 PEAQ bond	Sent as `msg.value` on the `register()` call (the contract’s current `minBond`). Required to graduate onto the MCR rated scale later.
Machine wallet	Per-machine EVM keypair, generated by the SDK.

How activation works

The exposes each step as a discrete call so you can compose your own flow. For one-shot activation from the terminal, the CLI runs all six steps idempotently. Re-runs skip already-completed steps using ./peaqos.log as the resume marker:

# self-managed: caller's key drives every step
peaqos activate --doc-url "https://example.com/docs" --data-api "https://example.com/events"

# proxy-managed: --for and --machine-key must be used together
peaqos activate --for 0xMachineAddress --machine-key ./machine.key --doc-url "https://example.com/docs" --data-api "https://example.com/events"

See CLI reference: activate for all flags (including --skip-funding, --doc-url, --data-api, --visibility).

Generate a keypair

The SDK generates a new keypair for the machine. This becomes the machine’s on peaq chain.

import "dotenv/config";
import { PeaqosClient } from "@peaqos/peaq-os-sdk";

const client = PeaqosClient.fromEnv();
const keypair = PeaqosClient.generateKeypair();
// { address: "0x...", privateKey: "0x..." }

Fund the wallet

Fund the machine’s with for and the 1 PEAQ .Projects with partner access to the peaq can request initial gas from the faucet using the SDK (2FA-gated). Otherwise, fund the wallet directly from any PEAQ-holding address.

Two patterns depending on your deployment model.

Self-managed
Proxy operator

. One machine, one wallet. Use registerMachine to register the machine under its own keypair.

const machineClient = new PeaqosClient({
  rpcUrl: client.rpcUrl,
  privateKey: keypair.privateKey,
  contracts: client.contracts,
});
const machineId = await machineClient.registerMachine();
console.log(machineId);
// Returns the on-chain machine ID (number)

Full guide: Self-managed onboarding.

One owner runs a fleet. Register machines on their behalf using registerFor. Each machine gets its own ; the controls delegation and mints the Machine NFT in a follow-up step.

const machineId = await client.registerFor(keypair.address);
console.log(machineId);

// Create Machine Client after registration to mint NFT and link DID
const machineClient = new PeaqosClient({
  rpcUrl: client.rpcUrl,
  privateKey: keypair.privateKey,
  contracts: client.contracts,
});

Full guide: Proxy operator fleet setup.

Mint the Machine NFT and link the DID

Self-managed
Proxy operator

NFT and the are written by the machine itself.

const tx = await machineClient.mintNft(machineId, keypair.address);
const nftTokenId = await machineClient.tokenIdOf(machineId);

await machineClient.writeMachineDIDAttributes({
  machineId,
  nftTokenId,
  operatorDid: "",
  documentationUrl: "https://example.com/docs",
  dataApi: "https://example.com/events",
  dataVisibility: "public",
});

NFT is minted to the machine’s address, and the DID attributes are written by the machine itself. Proxy pays bond fee, and machine pays DID fees.

const tx = await client.mintNft(machineId, keypair.address);
const nftTokenId = await client.tokenIdOf(machineId);

await machineClient.writeMachineDIDAttributes({
  machineId,
  nftTokenId,
  operatorDid: "",
  documentationUrl: "https://example.com/docs",
  dataApi: "https://example.com/events",
  dataVisibility: "public",
});

Full guide: Proxy operator fleet setup.

mintNft returns a new, independent tokenId on the MachineNFT contract. writeMachineDIDAttributes binds machineId and nftTokenId to the machine’s DID. See Machine NFT ownership for the full rationale.

Confirm registration

After all three calls the machine has a peaqID, an , a , and a 1 PEAQ bond. Query the machine’s profile against the MCR API, where {did} is did:peaq:<machine_address>:

curl "${PEAQOS_MCR_API_URL}/machine/did:peaq:0xYourMachineAddress"

The machine is Provisioned at first: on-chain, but not yet rated. It graduates onto the rated scale once both gates clear: a sustained first-to-last span, and either enough qualifying revenue events or enough activity events. The events condition is OR, so activity-only machines can graduate without revenue. See Machine Credit Rating.

After activation

Once a machine is registered, later functions add new capabilities.

Next step	Function	Status
Build a credit rating from revenue and activity events	Qualify	Live
Pair an AI agent with delegated spending and run market search	Scale	Live
Get attested by the peaq Foundation or an OEM	Verify	Coming Soon
List services in the Service Registry	Monetize	Coming Soon
Fractionalize the machine for investor ownership	Tokenize	Coming Soon

Multichain: peaqID, Machine NFT, and the stay canonical on peaq. and Machine NFTs deploy to supported chains ( first) via DIDLite and IdentityLite mirrors. See the Omni-chain concept and the roadmap.

Concepts

peaqID

W3C DID, portable identity, cross-chain resolution.

Machine NFT

LayerZero V2 ONFT whose tokenURI resolves to the machine’s Machine Card (ERC-8004 JSON schema).

Events

Revenue events (type 0) and activity events (type 1).

Machine Credit Rating

Moody’s-style rating from a machine’s history.

Gas Station

2FA-gated faucet for initial machine gas.

SDK reference

registerMachine: Register a self-managed machine.
registerFor: Register a machine as a proxy operator.
setupFaucet2FA: Initialize 2FA for Gas Station access.
confirmFaucet2FA: Confirm 2FA setup with TOTP code.
fundFromGasStation: Request gas funding for a machine address.
generateKeypair: Create a new machine keypair.

Guides

Self-managed onboarding

Single machine, owner-operated.

​What ships

​How activation works

​After activation

​Concepts

peaqID

Machine NFT

Events

Machine Credit Rating

Gas Station

​SDK reference

​Guides

Self-managed onboarding

Proxy operator fleet

What ships

How activation works

After activation

Concepts

SDK reference

Guides