Sato Hub
API / SDK

peaq

DePIN infrastructure providing agents with identity, wallets, and pay-per-request onchain settlement, with peaqOS skills for AI coding tools.

  • Sato Score68
  • ChainsMultichain
ActiveSelf-Reported

peaq is a partly open-source API or SDK by peaq Foundation, with no code activity tracked. Sato Score 68/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →

See how to install peaq →

No code activity tracked

Listed from peaq.xyz on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-19. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about peaq before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

peaq is a Layer 1 for DePIN whose peaqOS bundles decentralized identity, wallets, and data verification into an SDK so machines and agents can autonomously acquire compute, storage, data, and capital. peaqOS skills are designed to drop into AI coding tools (Claude Code, Cursor, Windsurf) with pay-per-request onchain settlement. The specific IDE-integration details are partly project-reported.

Sato Score

68/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
12/20
Interface verifiability
8/10
Docs & demo
10/10
Listing transparency & provenance
15/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v0.12.1 · as of 2026-10-24
Does it take your key?
Asks for a key
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from peaq.xyz on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-19.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.peaq.xyzas of 2026-10-24
Verification statusSelf-Reported — not independently reviewedself-reportedpeaq.xyzas of 2026-10-24
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/peaqnetwork2026-10-19
Website answersanswered (HTTP 200)observedpeaq.xyz2026-10-24
Daily check record90 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-23
Takes your keyasks for a private key or seed phrasedeclaredsatohub.aias of 2026-10-24
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-10-24
Built bypeaq Foundationconfidence 0.90self-reporteddocs.peaq.xyzas of 2026-06-25
Deploys asSDK, CLIconfidence 0.80self-reporteddocs.peaq.xyzas of 2026-06-25
Works withpeaqOS SDK, MCR API, ROS 2confidence 0.65self-reporteddocs.peaq.xyzas of 2026-06-25
Tagsdepin, machine-rwa, peaqos, agent-infrastructure, pay-per-request, identity, sd…confidence 0.75self-reportedpeaq.xyzas of 2026-06-25
Sato Score68/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-24

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Oct 19, 2026

Runtime: Node.js or Python 3.10+

pip install peaq-os-sdk python-dotenv
from peaq_os_sdk import PeaqosClient
client = PeaqosClient.from_env()
machine_id = client.register_machine()   # sends a 1 PEAQ bond

You supply: PEAQOS_NETWORK + PEAQOS_RPC_URL + PEAQOS_PRIVATE_KEY (funded wallet) + PEAQOS_GAS_STATION_URL + 6 contract addresses, ≥1 PEAQ for the bond

Read from the project’s own docs as of 2026-10-19. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-26

100%of 91 checks since 2026-07-26 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-24, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
68
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
Infrastructure, DePIN, Identity, Payments
Open source
Partial
Deploys as
SDK, CLI
Works with
peaqOS SDK, MCR API, ROS 2
Last checked
2026-10-24

Marketplace Signals

  • ▸ Demo available

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#depin#machine-rwa#peaqos#agent-infrastructure#pay-per-request#identity#sdk#robotics
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to peaq's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 19, 2026
    Verified: deploy spec
  2. Jul 27, 2026
    Sato Hub began tracking this listing
  3. Jun 25, 2026
    Enriched: supported integrations, tags
  4. Jun 25, 2026
    Auto-enriched: creator name, deployment options

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about peaq

Is peaq open source?
Partly. Some of peaq is published as source (https://github.com/peaqnetwork) and some is not. Checked as of 2026-10-24.
Which chains does peaq support?
peaq lists support for Multichain as of 2026-10-24.
Is peaq still maintained?
Sato Hub tracks no commit or release for peaq; it cannot say whether it is maintained.
How do I install or run peaq?
Node.js or Python 3.10+. Install: pip install peaq-os-sdk python-dotenv. Entry: from peaq_os_sdk import PeaqosClient client = PeaqosClient.from_env() machine_id = client.register_machine() # sends a 1 PEAQ bond. Sato Hub reproduced this install in a container on 2026-10-19.
Is peaq verified on Sato Hub?
Sato Hub holds one earned check for peaq: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 68 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "peaq — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/peaq

Data last refreshed 2026-10-24; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.