Payments for APIs.Built for agents.
Cleve is building payment infrastructure for software that buys data, compute, and services as it runs. We’re starting with API providers and the teams building AI agents.
How it works
Make a request.
Make a purchase.
A provider offers a service. A buyer authorizes spending. Software purchases what it needs. Cleve is being built to bring the whole exchange together.
Product conceptIllustrative amounts, not Cleve pricing.
For API providers
A new way to sell
access to your API.
Turn useful requests into a business. We’re designing Cleve for small, repeated purchases, with a clear view of what was bought and the value it creates.
Sell a useful result.Make access available one request at a time.
Understand what you earn.Connect each purchase to the work behind it.
Keep the outcome in view.See when a result needs a closer look.
Product conceptIllustrative amounts, not Cleve pricing.
For people building with agents
Give software permission
to spend with purpose.
Choose the services. Set the allowance. Keep the record. We’re designing a simpler way to let software make useful purchases within boundaries you understand.
The purchase stays in context.
Product conceptIllustrative amounts, not Cleve pricing.
Starting small. Thinking ahead.
Small purchases.
A wider network.
We believe payments can become a more natural part of how software works.
Cleve begins with APIs, with a longer-term ambition to connect more services, businesses, and forms of value.
A few things to know
At the
beginning.
A clearer picture of where
we are, and where we’re headed.
Help shape what comes next
Building an API
or an agent product?
We’re building for the people on both sides of the request.