Peaje makes any website or API ready for AI agents: discoverable, readable and, if you want, paid per request over HTTP 402, settled on Arbitrum and Robinhood Chain.
Live at https://usepeaje.com
Peaje is infrastructure that makes any website or API usable by AI agents: discoverable, readable and, optionally, payable per request over HTTP 402.
What it does:
Discovery on the business's own domain: llms.txt, openapi.json, agent cards, JSON-LD, an MCP server with the site's paid tools, and UCP/ACP/AP2 profiles, all generated from the dashboard and served at the site's domain.
Per-request payments: a priced route answers 402 with one offer per network. Agents pay in stablecoin via MPP or x402, with no account and no API key. On Arbitrum and Robinhood Chain, the PeajeSettlement contract credits the seller and the 2% fee on chain in the same transaction; sellers withdraw with a signature from their own wallet and no gas.
A public radar that scores any domain's agent readiness, and an AEO agent that measures whether ChatGPT, Perplexity, Gemini and Claude cite the site, writes the missing pages, hands tasks to the owner's coding tool over MCP, verifies the live site and re-measures at 2 and 6 weeks.
How it is built:
Three npm packages: @peaje/next (Next.js), @peaje/proxy (Express, Hono, Vite on Vercel) and @peaje/cli, which detects the framework and writes the integration.
A multi-tenant gateway (Hono + mppx on Railway) that verifies and settles payments, proxies paid requests to the origin and serves everything agents read. Postgres on Supabase; business and agent wallets on Privy; a Next.js dashboard on Vercel.
PeajeSettlement (Solidity, Foundry, OpenZeppelin): 70 tests with invariants, Slither clean, verified on Arbitrum Sepolia, Robinhood Chain, Arc and Tempo testnets. Settlements and withdrawals indexed by a subgraph on The Graph.
Repo: https://github.com/sandragcarrillo/peaje.