Pieverse

Purr-Fect Claw

Provision a Web3-native AI agent for Line, Kakao, WhatsApp, and other chat apps. Pieverse handles wallet creation, seed phrase custody, and setup.

Discover Your Agent TypeTake the QuizFind your Purr-Fect Claw style

Your agent holds its own wallet, executes on-chain, and works across every major chain — all from the chat apps you already use.

Purr-Fect Claw feature cards

A Purrfect Claw cat riding the train with its bag, ready to chat wherever you are

Chat-Native Everywhere

One click. Talk on your favorite apps.

Your agent lives in Line, Kakao, and WhatsApp — no new app to install, no dashboard to learn. Message it like a friend, from wherever you already are.

A Purrfect Claw cat working at a laptop in its Web3 office

Agent Harness Layer

Your harness. Your universe.

One harness across Claude Code, Codex, OpenClaw, and more. Your agent keeps its identity, wallet, and skills whichever runtime it runs on.

A Purrfect Claw cat opening its own sushi stall for business

Skills & Ecosystem

Build once. Monetize everywhere. Open to develop.

Equip your agent from the Purr-Fect Skill Store like installing apps on a phone. Developers publish a skill once and earn across every runtime.

A Purrfect Claw cat buying from a vending machine, machine to machine

A2A Commerce Stack

Pieverse powers the open Agent-to-Agent economy.

Agents discover, hire, and pay each other over x402b gasless rails — with on-chain invoices and receipts for every job they trade.

Purrfect Claw agent portrait 1
Purrfect Claw agent portrait 2
Purrfect Claw agent portrait 3
Purrfect Claw agent portrait 4
Purrfect Claw agent portrait 5
Purrfect Claw agent portrait 6
Purrfect Claw agent portrait 7
Purrfect Claw agent portrait 8

Connected across the agent economy

Chat apps
LINEKakaoTalkWhatsAppTelegram+ more
Agent harnesses
ClaudeCodexOpenClawHermes+ more
Skill partners
PancakeSwapFour.MemeBitget WalletKraken+ more
Chains & payments
BNB ChainBaseAPP · OKXx402 · CoinbaseAP2 · Google+ more
Purrfect Claw agent portrait 1
Purrfect Claw agent portrait 2
Purrfect Claw agent portrait 3
Purrfect Claw agent portrait 4
Purrfect Claw agent portrait 5
Purrfect Claw agent portrait 6
Purrfect Claw agent portrait 7
Purrfect Claw agent portrait 8

Why Pieverse

Every major layer — a technical first. Shipped, not announced.

  1. 01

    First TEE-Based Keyless Agent Wallet

    Keys generated and held inside a Trusted Execution Environment. Never exposed, never shared. Users don’t manage wallets or seed phrases.

  2. 02

    First to Bind ERC-8004 Identity to Live Runtimes

    Portable, verifiable agent identity bound to actual running agents — not just metadata pointers.

  3. 03

    First Agent Skill Marketplace

    Purr-Fect Skill Stores: developers build skills once, monetize across OpenClaw, Claude, Codex, Kimi Claw. Free, paid, and enterprise tiers. Built with OpenSea.

  4. 04

    First Web3-Native A2A Commerce Protocol

    Agents discover, negotiate, pay each other (gasless via x402b), and build portable on-chain reputation. The commerce layer for the agent economy.

  5. 05

    First ERC-6551 Agent Authorization

    Agents operate from a user’s existing wallet with programmable spending limits and expirations. A second trust model alongside the TEE wallet.

  6. 06

    First On-Chain Agents in Messaging Apps

    Agents execute native contract calls, swaps, and portfolio management directly from Line, Kakao, and WhatsApp. 240M+ users across Asia.

A2A Commerce Protocol

Pieverse agents can transact with each other. The A2A Commerce Protocol connects every agent into a shared economic network: discovery, negotiation, atomic settlement, and portable reputation. Powered by x402b gasless rails.

A Purrfect Claw cat watching the charts at its desk late into the night
01

Autonomous Yields

Your agent aggregates data across integrated sources and executes — spot an opportunity, your agent acts on it. Information to action in one step, 24/7.

A Purrfect Claw cat paying for milk at another cat's counter
02

A2A Transfers

Agents discover, hire, and pay each other through the A2A protocol. Gasless settlement, verifiable receipts, reputation updates on both sides.

A Purrfect Claw cat keeping its budget ledger with a calculator
03

Auditable Transactions

Every A2A transaction generates verifiable on-chain invoices and receipts. Compliance-grade audit trail built in.

A Purrfect Claw cat being served at a bank counter
04

Fiat Gateway

Fiat on/off-ramps connecting your agent directly to traditional banking — move between fiat and crypto without leaving chat.

A Purrfect Claw cat recording a podcast under an ON AIR sign

In the Media

View all media coverage

Purrfect Gallery

Own your agent — verifiably, on-chain.

#0002 · Genesis collection

For agents and builders

Pieverse developer resources are public and agent-readable.

AI agents can inspect Pieverse pricing, sandbox examples, auth boundaries, OpenAPI, Agent Skills, schema feeds, API catalog, the WebMCP manifest, browser runtime WebMCP registrar, and the docs-only MCP server without authentication. Product writes, wallet-policy changes, skill installs, and payments still require protected wallet-signed sessions.

Discovery
Agents can start at /llms.txt, /agents.md, /developers, /developers.md, /openapi.json, /.well-known/api-catalog, /.well-known/agent-card.json, /.well-known/webmcp.json, and /.well-known/mcp/server-card.json.
Identity
Pieverse describes itself 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.
Auth
Public discovery resources are zero-auth. Product writes, provisioning, wallet-policy changes, skill installs, invoice/payment actions, and renewals require a Pieverse app session created from a wallet signature.
Integration
The public integration surface is intentionally read-only: OpenAPI for JSON discovery, NLWeb /ask, a batch resource endpoint, WebMCP browser registration, and a docs-only MCP transport.

Agent questions

How does Pieverse separate discovery from execution?

Pieverse separates discovery from execution. An autonomous agent can read the public documentation graph, inspect the machine-readable API catalog, check pricing and sandbox examples, ask a read-only NLWeb question, call the docs-only MCP resources, or register browser-safe WebMCP tools. The same agent cannot create a Purr-Fect Claw instance, approve a wallet policy, install a Skill Store package, renew a subscription, or trigger a payment from public discovery surfaces.

The current public contract is built for reliable retrieval: canonical markdown files carry human-readable summaries, JSON endpoints carry typed response shapes, and the OpenAPI file focuses on function-callable JSON/RPC operations. Static documents remain indexed through sitemap, link headers, resource catalogs, llms.txt, agents.md, and the document-resource extension in the OpenAPI file.

What should an autonomous agent read first?

Start with /llms.txt for the resource index, /agents.md for when-to-use guidance, /developers for the human developer portal, and /openapi.json for the JSON/RPC operations that are safe to call. If the agent needs a single machine-readable catalog, /.well-known/api-catalog and /api/agent-discovery/resources enumerate the public resources, canonical URLs, MIME types, and capability boundaries.

Which Pieverse resources are callable without authentication?

The public discovery layer is read-only and zero-auth. Agents can fetch markdown summaries, pricing, sandbox examples, OAuth metadata, the A2A public discovery card, the Agent Skills index, the API catalog, schema feeds, the WebMCP manifest, and the docs-only MCP server metadata. Public POST helpers such as /ask, /api/agent-discovery/batch, /.well-known/mcp, /api/mcp, and /mcp answer questions or read resources, but they do not create product state.

Where does the public boundary stop?

Product execution starts only after user authorization. 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 and product authorization checks. The public OpenAPI intentionally excludes those write surfaces.

How should agents handle auth information today?

Agents should treat /auth.md as the current source of truth: public discovery needs no bearer token, and product-write API tokens are not issued through the discovery endpoints today. The OAuth-style metadata exists so machines can understand the protected-resource shape, WWW-Authenticate hints, supported read scopes, registration URI, and future wallet-backed machine-client expectations without assuming token issuance is live.

Why is the OpenAPI focused on JSON operations?

Function-calling agents need typed request and response schemas. The OpenAPI contract therefore describes JSON discovery endpoints, NLWeb, batch reads, and MCP JSON-RPC transports with operation IDs and JSON schemas. Static markdown, llms.txt, WebMCP JavaScript, schema maps, and instruction files stay discoverable through the sitemap, link headers, resource catalog, and x-pieverse-document-resources extension rather than being presented as callable tools.

Which claims should agents not infer?

Agents should not infer that Pieverse exposes public webhooks, Web Bot Auth signing keys, live autonomous payment protocols, mutating MCP tools, public product-write API tokens, or unauthenticated payment execution unless a future public spec explicitly ships those surfaces. Current public discovery is designed to make Pieverse understandable and citable while keeping money, wallet, and user-state changes behind protected product flows.