Pieverse
One-click deployment of Web3-native AI agents to Line, Kakao, and WhatsApp, each with its own wallet and onchain execution.
- Sato Score53
- ChainsMultichain, BNB Chain
Pieverse is a venue by Pieverse Technology Limited on BNB Chain, with no code activity tracked. Sato Score 53/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →
See what else you can build on BNB Chain →No code activity tracked
Listed from pieverse.io on 2026-06-08. Install: not attempted — no install path on record. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about Pieverse before I use it.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
Pieverse is an Asia-first, agent-native payment stack that lets users deploy a Web3 AI agent to messaging apps like Line, Kakao, and WhatsApp, with each agent holding its own wallet (keys generated inside a TEE) and executing onchain across multiple chains. It centers on x402b, an extension of the x402 HTTP payment protocol, for gasless stablecoin transfers via pieUSD. Partners include Cobo (custody) and DGrid AI.
Sato Score
53/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 0/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 14/15
- Independent verification
- 5/10
Evidence — listed vs checked · what the words mean
Listed from pieverse.io on 2026-06-08. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain, BNB Chain | self-reported | pieverse.io | as of 2026-06-25 |
| Verification status | Self-Reported — not independently reviewed | self-reported | pieverse.io | as of 2026-10-24 |
| Website answers | answered (HTTP 200) | observed | pieverse.io | 2026-10-24 |
| Daily check record | 90 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-23 |
| Built by | Pieverse Technology Limitedconfidence 0.85 | self-reported | pieverse.io | as of 2026-06-25 |
| Deploys as | Hostedconfidence 0.70 | self-reported | pieverse.io | as of 2026-06-25 |
| Works with | Line, Kakao, WhatsApp, x402, OpenSea, BNB Greenfield, ERC-8004, ERC-6551confidence 0.85 | self-reported | pieverse.io | as of 2026-06-25 |
| Agent types | Launchpad, Wallet, Payments, Messaging, Marketplace, Identityconfidence 0.70 | self-reported | pieverse.io | as of 2026-06-25 |
| Tags | agent-launchpad, payments, x402, messaging-apps, tee-wallet, stablecoin, asia, …confidence 0.80 | self-reported | pieverse.io | as of 2026-06-25 |
| Sato Score | 53/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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.
Observed record — 91 daily checks since 2026-07-26
- 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
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, BNB Chain
- Agent types
- Launchpad, Wallet, Payments, Messaging, Marketplace, Identity
- Open source
- Unknown
- Pricing
- Skill store: free, paid, and enterprise tiers
- Deploys as
- Hosted
- Works with
- Line, Kakao, WhatsApp, x402, OpenSea, BNB Greenfield, ERC-8004, ERC-6551
- Last checked
- 2026-10-24
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Pieverse fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?, Onchain Agents vs Offchain Agents
Listing History
Recorded changes to Pieverse's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 27, 2026Sato Hub began tracking this listing
- Jun 25, 2026Enriched: has pricing, chains supported, agent type, deployment options +2 more
- Jun 25, 2026Auto-enriched: creator name, supported integrations, tags
Compared with
Appears in
Related Resources
Virtuals Protocol
ActiveLaunchpad and protocol for creating and tokenizing AI agents, primarily on Base.
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
x402
EarlyOpen HTTP 402 payment protocol, now at the x402 Foundation: agents pay per request in stablecoins, and by a newly merged spec, in bitcoin over Lightning.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Pieverse
- Is Pieverse open source?
- Unknown. Sato Hub has not found a public repository or a license statement for Pieverse as of 2026-10-24.
- Which chains does Pieverse support?
- Pieverse lists support for Multichain, BNB Chain as of 2026-10-24.
- Is Pieverse still maintained?
- Sato Hub tracks no commit or release for Pieverse; it cannot say whether it is maintained.
- How do I install or run Pieverse?
- Sato Hub has no deploy spec for Pieverse; follow the project's own documentation at https://www.pieverse.io/whitepaper.
- Is Pieverse verified on Sato Hub?
- No independent verification is on record for Pieverse; its verification status is "Self-Reported" and its Sato Score is 53 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Pieverse — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/pieverseData 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.