Pieverse (PIEVERSE)

Overview

Pieverse is a Web3 platform for AI agents that can hold wallets, use on-chain tools, and make payments. An AI agent is software that carries out tasks on a person’s behalf. Pieverse’s Purr-Fect Claw product lets people set up agents for chat apps such as LINE, KakaoTalk, and WhatsApp. Its wider system includes a place for developers to publish agent skills and payment tools that create invoices and receipts. PIEVERSE is the project’s ecosystem token. (pieverse.io)

The project grew from a focus on business-ready crypto payments. A blockchain transfer shows that funds moved, but a business may also need to know what was purchased, who requested payment, and when the work was completed. Pieverse aims to connect those details to verifiable records. That payment work now sits alongside its tools for agents that act for users or transact with other agents. (pieverse.io)

History & Team

From payment records to AI agents

Pieverse’s early plans centered on timestamping: creating dated, verifiable records for invoices, payments, and receipts. Its November 2025 white paper described x402b, a system designed for agent-friendly stablecoin payments. The project later expanded its public focus to agent-managed accounts, chat-based agents, and the Purr-Fect Claw runtime. Pieverse’s press page places its Agentic Neobank launch in December 2025 and its Purr-Fect Claw launch in March 2026. (pieverse.io)

Pieverse identifies Colin as its co-founder and chief executive officer and David as its co-founder and chief marketing officer. Its published team description also names staff responsible for business development, technology, and ecosystem growth. In October 2025, Pieverse reported a $7 million strategic funding round co-led by Animoca Brands and UOB Ventures. A separate project filing names Pieverse Collective Limited, incorporated in the British Virgin Islands, as the entity seeking admission of PIEVERSE to trading in the European Union. (pieverse.io)

Technology & How It Works

An agent with a wallet and skills

Purr-Fect Claw gives an agent an identity and a wallet linked to its software instance. Pieverse’s developer documentation describes a trusted execution environment, or TEE, as the hardware-isolated setting used for wallet keys. The agent can use a command-line tool called purr to check balances, request signatures, transfer assets, and carry out supported on-chain actions. Each instance maps to one wallet. (docs.pieverse.io)

Skills tell an agent how to complete a type of task, such as checking a balance or routing a swap. Pieverse’s Skill Store lets developers package and publish those instructions for others to install. Public developer materials can be read without signing in, while actions that change an agent, its wallet settings, installed skills, or payment state require an authorized session. This separates learning about available tools from using them to move funds or change an account. (docs.pieverse.io)

Payments and receipts

Pieverse’s x402b design extends x402, a way for software to request payment through a web interaction. It uses a relayer to handle the blockchain transaction fee, so the person or agent making a payment does not have to pay that fee directly in a separate step. The white paper describes pieUSD, a wrapped form of USDT, as a payment asset for this design. PIEVERSE serves a different role as the ecosystem token. (pieverse.io)

Pieverse also links payments to structured records. An invoice states what is owed; a receipt records that a payment took place. Timestamps and blockchain records can make those documents easier to check later. For agents hiring and paying one another, this gives both sides a record of the job and its settlement rather than only a token-transfer entry. (pieverse.io)

Tokenomics & Utility

Supply and allocation

PIEVERSE has a fixed total supply of 1 billion tokens. Project documents describe versions on Ethereum and BNB Smart Chain. The published allocation divides the supply into five groups: (pieverse.io)

• 27.6% for community growth, including participation rewards.
• 27.4% for ecosystem development and marketing.
• 20% for the team and advisers.
• 15% for strategic investors.
• 10% for the foundation reserve. (pieverse.io)

The white paper describes PIEVERSE as a way to support governance, rewards, access to features, and discounts on some platform fees. It also outlines staking and incentives for ecosystem activity. These uses explain the token’s planned role, while the practical range of token-based services depends on the products and governance features Pieverse develops. Some team and investor allocations are subject to vesting, meaning their tokens are released over time. (pieverse.io)

It helps to keep the platform’s two assets distinct. pieUSD is described as a stablecoin-based payment tool for settling transactions. PIEVERSE is the token tied to participation and incentives across the broader ecosystem. An agent could therefore use Pieverse’s payment infrastructure without every invoice being denominated in PIEVERSE. (pieverse.io)

Ecosystem & Use Cases

Pieverse brings together chat apps, agent runtimes, wallets, developer skills, and payment records. A user can communicate with an agent in a familiar messaging app while the agent uses its wallet and installed tools to perform supported on-chain tasks. The project also describes compatibility with agent frameworks including OpenClaw, Claude Code, Codex, and Hermes Agent. (pieverse.io)

For developers, the Skill Store offers a way to publish reusable abilities. Pieverse’s documentation describes skills for tasks such as token transfers, swaps, lending, and other wallet actions. For businesses and freelancers, the invoice-and-receipt layer is aimed at giving crypto payments a clearer business purpose. A payment for a service can be paired with a request, a settlement record, and a dated receipt. (docs.pieverse.io)

Pieverse also describes an agent-to-agent commerce model. In it, one agent can find another to do a task, arrange payment, and record the result. For example, an agent obtaining data for a user could pay an agent that provides the data and keep a receipt for the exchange. This model connects Pieverse’s agent tools with its earlier work on payment records. (pieverse.io)

Advantages & Challenges

Pieverse’s main strength is the way its parts fit together. Chat-based access can make agents easier to use, while wallets and skills give them ways to act on a blockchain. Invoices and receipts add context to payments that would otherwise appear as plain transfers. The relayer-based payment design also aims to remove a separate gas-payment step from routine transactions. (pieverse.io)

The challenge is coordination. An agent needs the right skills, wallet permissions, payment method, and records for each task. Work across different chains and outside services adds more steps. Pieverse addresses part of this through scoped authorization and a shared skill system, but its wider vision depends on developers publishing useful tools and on services accepting agent-led transactions. Community governance and broader integrations are also part of the project’s stated development plans. (pieverse.io)

Where to Buy & Wallets

PIEVERSE is available for spot trading on Kraken and KuCoin. Binance has also offered PIEVERSE through Binance Alpha, which is a separate product from a standard Binance spot listing. Exchange access and supported deposit networks vary by location and platform. (blog.kraken.com)

PIEVERSE exists on Ethereum and BNB Smart Chain, so it can be held in a wallet that supports tokens on the relevant network. The network selected for a withdrawal must match the receiving wallet’s network. Pieverse’s agent wallet has a different job: it gives a configured AI agent an address for carrying out authorized on-chain actions. The project’s token documents identify the contract addresses for its Ethereum and BNB Smart Chain versions. (pieverse.io)

Regulatory & Compliance

Pieverse’s issuer published a white paper for PIEVERSE under the European Union’s Markets in Crypto-Assets framework, known as MiCA, in connection with admission to trading. The filing describes PIEVERSE as an “other crypto-asset” and identifies Pieverse Collective Limited as the entity seeking that admission. It also describes the token’s functions and proposed governance role. (pieverse.io)

In the United States, the legal treatment of a crypto asset can depend on its features and how it is offered or sold. The U.S. Securities and Exchange Commission’s guidance treats those as fact-specific questions. Separately, businesses using Pieverse’s payment records remain responsible for the tax, reporting, identity-check, and recordkeeping rules that apply to their activities and jurisdictions. A timestamped receipt can support those tasks by preserving transaction details. (sec.gov)

Shariah compliance raises a different question. Pieverse’s documented agent tools include lending, and Islamic finance generally prohibits interest-bearing lending under the rule against riba. That lending capability means the wider Pieverse ecosystem does not meet a strict interest-free Shariah screen. Its invoicing and payment-record features are separate activities, so a religious assessment of a particular use would depend on the transaction involved. (docs.pieverse.io)

Future Outlook

Pieverse’s direction links three ideas: agents that people can use through chat, skills that developers can share, and payments that leave useful records. Its published plans include wider chain support, more integrations, and community governance. The project’s long-term role will depend on whether those pieces work together well enough for regular tasks, from paying for digital services to documenting work done by one agent for another. (pieverse.io)

The clearest measure of that vision is practical use. Agents need to complete tasks within their permissions, developers need ways to distribute helpful skills, and payment records need to be useful to the people and organizations receiving them. Pieverse’s products are built around those needs. (pieverse.io)

Summary

Pieverse combines AI-agent wallets and skills with tools for verifiable crypto payments. PIEVERSE supports the project’s ecosystem model, while its payment design uses stablecoin-based settlement and linked invoices and receipts. Its place in Web3 rests on a simple goal: making on-chain actions easier for agents to carry out and easier for people to understand afterward. (pieverse.io)