Skip to main content
AI agents are becoming the primary way people reach APIs. They don’t sign up, they don’t enter cards, and they won’t wait for an invoice — but they can pay an HTTP 402 in the same request. Proceeds is how you sell to them: wrap your API, publish discovery so agents can find you, and manage the payments that follow.

​
Why sell to agents?

Most agent users have never called a traditional API before. Pay-per-request pricing opens a customer segment your subscription tiers never reach. No key provisioning, no billing portal, no human checkout.

​
What you will do

  1. Wrap your API with a service and paywalls
  2. Publish discovery so agents know price and how to call you
  3. Share payment URLs — or let registries find you
  4. Monitor and settle

​
1. Wrap and price your API

Create a service pointing at your origin, then add a paywall per billable route. Include Tempo if you want MPP URLs. Keep EVM chains (for example Base) for x402. Prefer clear slugs and descriptions — agents and discovery docs reuse them.

​
2. Publish discovery

Agents should know cost and usage before they hit 402. Configure categories, docs links, llms.txt, public routes, and x-guidance on the service. Proceeds publishes OpenAPI documents for MPP discovery and x402scan. Walkthrough: API discovery.

​
3. Let agents pay

Buyers typically use AgentCash, Tempo Wallet, or Circle Agent Stack. Smoke-test yourself: Make your first payment.

​
4. Monitor and settle

​
Tips

Create a service

Start wrapping your API.

API discovery

Publish OpenAPI payment terms.