Pieverse (PIEVERSE)

What Pieverse is

Pieverse is a platform that puts AI agents with their own crypto wallets inside consumer messaging apps. Its site describes it as "a web3 AI agent platform where Purr-Fect Claw provisions user-owned agents, Skill Store adds capabilities, and wallet-signed sessions protect product actions," and says an agent "holds its own wallet, executes on-chain, and works across every major chain — all from the chat apps you already use" (source: Pieverse, pieverse.io, read September 2026).

The target surface is messaging rather than a dashboard. Pieverse names LINE, KakaoTalk, WhatsApp and Telegram as the chat apps its agents live in, and states that these represent "240M+ users across Asia."

The company behind it is named on its own site as Pieverse Technology Limited.

For where to buy Pieverse from your country or state, see the availability tables on this page and the venues listed at Exchanges.

How it works

The wallet design is the foundational piece and the one Pieverse leads with. Its developer documentation says that "purr gives your agents a TEE-secured wallet — no key management required," and explains the mechanism: "Your purr wallet is secured by a Trusted Execution Environment (TEE). Private keys are generated and stored in hardware-isolated memory and are never exposed to your skill code, the runtime, or anyone else."

That is a specific claim about where a private key lives. The agent can check balances, get addresses, transfer assets, sign messages and execute operations "without ever touching a private key," and the user is not asked to manage a seed phrase.

Pieverse describes a second authorization model alongside it, built on ERC-6551, where "Agents operate from a user's existing wallet with programmable spending limits and expirations." The two models differ in who holds the funds: a TEE wallet the agent owns, or a spending allowance carved out of a wallet the user already controls.

Identity uses ERC-8004. Pieverse claims to be the first "to Bind ERC-8004 Identity to Live Runtimes," describing "Portable, verifiable agent identity bound to actual running agents — not just metadata pointers." The same agent identity, wallet and skills are meant to persist across runtimes, which the site lists as Claude Code, Codex, OpenClaw and Hermes Agent.

Capabilities come from a marketplace. The Skill Store is described as working "like installing apps on a phone," where "developers publish a skill once and earn across every runtime," with free, paid and enterprise tiers, and the site says it is "Built with OpenSea." Its named skill partners include PancakeSwap, Four.Meme, Bitget Wallet and Kraken.

The commercial layer is agent-to-agent. Pieverse describes an A2A Commerce Protocol where "Agents discover, hire, and pay each other over x402b gasless rails — with on-chain invoices and receipts for every job they trade," covering "discovery, negotiation, atomic settlement, and portable reputation." Chains and payment rails named on the site include BNB Chain, Base, OKX, x402, Coinbase AP2 and Google.

One boundary is drawn firmly in the documentation, and it is worth repeating because it constrains what an autonomous agent can do to a Pieverse account. Public discovery is read-only and requires no authentication, while "Creating or renewing a Purr-Fect Claw instance, changing wallet policies, installing Skill Store packages, approving on-chain actions, creating invoice/payment state, and using protected A2A or merchant SDK workflows require a wallet-signed Pieverse session."

Supply and tokenomics

The Pieverse site and developer documentation read for this page publish no token supply, no allocation table, no emission schedule and no description of what the PIEVERSE token does within the product. The documentation covers the purr command-line tool, the Skill Store and the discovery surface; it does not carry a tokenomics page.

That gap is stated here rather than filled from a secondary source. Anyone assessing the token as an asset, rather than the platform as a product, is working without published tokenomics.

The token contract appears at the same address, 0x0e63b9c287e32a05e6b9ab8ee8df88a2760225a9, on BNB Chain and on Ethereum. Read the supply from the data on this page rather than from a secondary source, and note that a supply figure taken from a block explorer is not the same as a published allocation.

History

Pieverse's product bet is about distribution rather than about model capability. Rather than building another agent framework, it targets the chat applications people in Japan, Korea and much of Southeast Asia already use every day, and puts a wallet-carrying agent inside them.

The "harness layer" idea follows from that. Pieverse describes running "One harness across Claude Code, Codex, OpenClaw, and more" so an agent "keeps its identity, wallet, and skills whichever runtime it runs on." That is a bet that agent runtimes will proliferate and that identity, wallet and skills should outlive whichever one is in fashion.

The company's public claims are framed as firsts, and its own site lists six: the first TEE-based keyless agent wallet, the first binding of ERC-8004 identity to live runtimes, the first agent skill marketplace, the first web3-native agent-to-agent commerce protocol, the first ERC-6551 agent authorization, and the first on-chain agents in messaging apps. The site notes Forbes "referenced Pieverse in a positive context while discussing the missing layers of trust, settlement, and interoperability in agentic commerce," published 29 March 2026.

The developer surface is unusually explicit about what machines may and may not do. Pieverse publishes discovery endpoints at /llms.txt, /agents.md and /openapi.json, and states plainly which claims an agent should not infer, including that it exposes "public webhooks, Web Bot Auth signing keys, live autonomous payment protocols, mutating MCP tools, public product-write API tokens, or unauthenticated payment execution."

Risks and what to watch

A Trusted Execution Environment is a hardware trust assumption, not the absence of one. Keys held in hardware-isolated memory are protected from the runtime and the skill code, and they still depend on the enclave's implementation, its vendor and its patch history. TEE vulnerabilities are a documented category of attack in their own right.

Agents that hold funds and execute transactions autonomously introduce a failure mode ordinary wallets do not have. A prompt-injected or malfunctioning agent with spending authority can transact wrongly at machine speed. The ERC-6551 model with programmable spending limits and expirations is the documented mitigation; a limit is a cap on the damage, not a prevention.

Skill Store packages are third-party code granted access to an agent's capabilities. The security of an installed skill is the security of whoever wrote it.

Platform dependency runs through the whole product. Agents live inside LINE, KakaoTalk, WhatsApp and Telegram, and each of those platforms sets its own rules about bots, commerce and financial activity. Those rules can change.

Finally, the reach and partner figures on this page are Pieverse's own. "240M+ users across Asia" describes the user base of the messaging platforms, not of Pieverse.

Frequently asked questions

What is Purr-Fect Claw?

Pieverse's provisioned agent. It gives a user a web3-native AI agent for LINE, KakaoTalk, WhatsApp and other chat apps, with Pieverse handling wallet creation and setup so the user manages no seed phrase.

How does the agent hold a wallet without exposing keys?

Through a Trusted Execution Environment. Pieverse's documentation says private keys "are generated and stored in hardware-isolated memory and are never exposed to your skill code, the runtime, or anyone else."

Can an autonomous agent spend from a Pieverse account without permission?

No, per the documentation. Public discovery is read-only, while creating instances, changing wallet policies, installing skills, approving on-chain actions and triggering payments all require a wallet-signed Pieverse session.

What does the PIEVERSE token do?

The site and developer documentation read for this page do not say. They document the platform, the wallet model, the Skill Store and the agent-to-agent commerce protocol, but publish no token utility, supply or allocation.

Where can you buy Pieverse?

Availability depends on your country or US state. See where to buy Pieverse for the exchanges serving your jurisdiction, and Exchanges to compare fees, kyc requirements and supported payment methods.