AI agents can buy services. CAPI2 makes the transaction verifiable.

The problem

AI agents can call APIs, but commercial use still breaks at the boundaries. The agent may not know what an endpoint costs, whether it is allowed to spend, whether the promised result was delivered, or how to retain evidence of the exchange. Traditional checkout flows, API-key onboarding and monthly subscriptions were designed for humans, not software acting within a limited mandate.

What CAPI2 built

CAPI2 exposes services through OpenAPI, agent manifests, llms.txt and x402 discovery. A buyer can inspect the price and terms, receive an HTTP 402 payment requirement, settle in USDC on Base and retry the same request with proof. The response is delivered inline as structured JSON. CAPI2 adds preflight policy checks, claim verification, endpoint health, domain-security observations, manifest checks, receipt validation and a combined risk report.

Where AI is central

The customer is often an AI agent. The interfaces are deliberately machine-readable so ChatGPT-compatible tools, MCP clients and other autonomous systems can decide when a service is useful and consume the result without a human-operated dashboard. CAPI2 keeps evidence extraction and payment controls deterministic where possible: an agent can reason with the result, while the commerce layer does not ask a language model to invent whether payment or delivery occurred.

What makes it different

CAPI2 is not a token scheme and it does not promise investment returns. It sells small, concrete digital outcomes. Spending authority can be capped, risky contract terms remain blocked, tests are separated from organic revenue, and a payment can never be presented as a customer sale without independent evidence. That distinction matters for autonomous systems, where a confident status message is not the same as an auditable event.

Current proof—and the honest limitation

The production service publishes twelve paid resources and has completed verified x402 canary transactions that prove the payment-to-delivery loop. A persistent revenue worker now records sequential runs in Postgres and monitors production, discovery, buyer intent and settlements. At publication time CAPI2 has no confirmed organic customer revenue. Canary and owner-funded tests are explicitly excluded. The next milestone is therefore not another feature count; it is a first independently verified buyer.

What comes next

CAPI2 is looking for AI-agent builders, API operators and design partners who need safer pay-per-use commerce. The immediate offer is a free public endpoint preview followed by a $29 Website & API Risk Report. Findings arrive as JSON plus Markdown, with prioritized actions covering security headers, TLS, machine discovery and x402 readiness.