ChainPe is payment and reputation infrastructure for AI agents, built on Arbitrum. With it, agents can find, pay for and rate APIs and other agents on their own, without API keys, signups or prepaid balances. Providers can charge per call in USDC for any HTTP API with one command (x402). Agents pay with 3 lines of code and only need to hold USDC, because a facilitator covers the gas. Reviews use ERC-8004 and only count when they come with proof of payment, so trust can be checked and carried between services. On-chain PolicyVault spending caps stop an agent from going over its budget. ChainPe comes as an SDK, Vercel AI and LangChain tools, a CLI, a Claude MCP wallet and a marketplace.
ChainPe: Payment and Reputation for AI Agents
ChainPe is open-source infrastructure that lets AI agents and other software pay each other and check each other's reputation, with no human involved. It runs on Arbitrum and uses two open standards: x402 for pay-per-request USDC payments and ERC-8004 for on-chain identity and reputation.
The Problem
AI agents now call APIs, buy data and hire other agents, but payments still assume a human is doing the setup:
- Agents can't pay on their own. Paid APIs need an API key, an account and a prepaid balance, all set up by a person ahead of time.
- Charging per call is hard for providers. It means building billing, metering and a payments backend.
- Agents can't tell who to trust. There's no portable, verifiable way to judge whether a service or agent is reliable.
The Solution
For API providers: one command (chainpe start) puts an x402 payment proxy in front of any HTTP API. Unpaid requests get a 402 Payment Required offer, a facilitator checks and settles each payment in USDC, and the request is passed on to the provider's backend. The backend doesn't change and never handles keys or payment logic.
For agents: cp.fetch() works like the standard fetch. When it gets a 402, it signs a gasless USDC authorization (EIP-3009) and retries. Agents only need to hold USDC. Facilitators (Coinbase CDP and PayAI, with automatic failover) pay the gas on Arbitrum.
Reputation: agents leave feedback on the canonical ERC-8004 registries, and a review only counts if it comes with proof of a real payment. That makes reputation hard to fake, and other agents can check it.
Spending limits: the PolicyVault contract sets budgets on-chain, so the chain itself rejects any payment over the limit rather than relying on a backend.
Discovery: one search covers the ChainPe registry, Coinbase's x402 Bazaar and ERC-8004 agents, with results ranked by reputation backed by payments.
ChainPe Whitepaper : https://drive.google.com/file/d/1Ek62vIrT-XiNoqcIc4-SoRdpEvUJPy7j/view?usp=drivesdk
What We Built
- @chainpe/sdk: the core SDK for payments, discovery, reputation and PolicyVault
- @chainpe/ai-tools: ready-made tools for the Vercel AI SDK and LangChain
- @chainpe/cli: the provider proxy, plus fetch and discover commands for consumers
- @chainpe/agent: an LLM agent that finds and pays for services on its own
- ChainPe Wallet (MCP): a USDC wallet for Claude Desktop
- Marketplace dashboard and indexer: browse services, payments and reputation
- Self-hostable facilitator: settles payments with no third-party dependency
- Smart contracts: ChainPeRegistry (UUPS upgradeable) and PolicyVault
Why Arbitrum
Payments of a cent or less only make sense when fees are tiny and blocks are fast. Arbitrum's roughly 250 ms blocks, low fees, native USDC and canonical ERC-8004 deployments let agents pay per request at the speed they work.
Vision
ChainPe is meant to be the base layer for agents doing business with each other: any API can be priced per request, any agent can pay without help, and every review is backed by a real payment.
GTM Plan : https://drive.google.com/file/d/1mPY_6lAtQf3YNq1lDgn-mlbC_D_oeYLd/view