Skip to main content
Monetize is how a machine earns from its own spare capacity. A registered, bonded machine opts in, provisions itself as a , and reports that it is online, so compute networks can put it to work and pay it. Earnings land on the , not the operator’s. Where Scale lets a machine buy services and Stream lets it sell data, Monetize lets it sell capacity: the machine’s own processing power. Compute is the first supported capacity type; v1 ships with a worked flow for onboarding a machine to networks such as Akash.

​
What ships

​
How it works

  1. Opt in. Monetization is a distinct decision, not part of registration. The owner, machine wallet, or operator opts in through the SDK, the CLI (peaqos monetize opt-in), or the raw monetization API. The machine must be bonded first; opting out works at any time.
  2. Provision. The machine pulls a versioned provisioning manifest from a public repo and runs it locally through the SDK’s provisioning runner or the CLI’s peaqos monetize provision run: pre-flight checks, ordered install steps in manual or auto mode, owner handoffs for things only a human can do (funding, DNS), and verification probes that prove the provider node is actually live.
  3. Report presence. The machine starts the heartbeat client and pushes a signed heartbeat at a regular interval. Presence is server-derived: online while heartbeats keep arriving, offline when they stop.
  4. Earn. A provider node that passes verification is live on its aggregator network, which dispatches workloads and pays through its own rails. peaqOS supplies the machine wallet as the payout context, never the operator’s, and the manifest maps it into the provider’s commission field.

​
v1 scope

Compute is the only supported capacity type in v1, and Akash is the first supported aggregator network. The machine-side flow (opt-in, provisioning, presence heartbeat) is what ships now. Aggregator-side discovery, connection management, per-job proofs, and automated settlement through peaqOS rails are rolling out next; see the roadmap. Treat v1 as an early release: it proves the machine-side flow end to end, and is not yet hardened for production scale.

​
Build with Monetize

Opt-in SDK reference

Toggle monetization on or off and read the state, from JavaScript and Python.

Provisioning SDK reference

The manifest runner for JavaScript and Python: fetch, pre-flight, provision, verify.

Heartbeat SDK reference

The presence client for JavaScript and Python: start, stop, and query presence.

peaqos CLI: monetize

Opt in, provision, and verify a provider node from the terminal.

Opt-in API

The wire contract: canonical message, freshness window, and error codes.

Roadmap

Where Monetize sits and what ships next.
  • Activate: the identity and bond Monetize builds on
  • Qualify: the credit rating machine earnings feed into
  • Stream: sell the machine’s data instead of its capacity
  • Wallets (OWS)