Sell an API Product

API products are bought by people who understand infrastructure, so the pitch is the metrics: paying customers, calls per month, error rate, and how many customers would notice if the service stopped for an hour.

Usage-based revenue is priced a little below subscription revenue because it moves with customers' seasons. A few enterprise customers on contracts change that fast.

What buyers pay

Two to three and a half times annual revenue, more with contracts

Buyers discount for concentration: if the top three customers are half the revenue, the price reflects the risk of losing one. Signed annual contracts that can be assigned go the other way.

Infrastructure cost is checked closely. An API that spends most of its revenue on compute is priced on the margin.

Ranges reflect small-deal marketplaces in 2026 and move with the market. Your buyer decides the price; these numbers tell you where the conversation starts.

Before you list

1. Revenue by customer for twelve months, anonymised, with contract terms where they exist.
2. Uptime history and the incident log.
3. Infrastructure diagram and monthly cost by component.
4. Documentation site analytics and the developer signup funnel.
5. A key rotation plan that lets customers keep working through the transfer.

What moves at closing

The buyer pays Tool Index once you've both signed. Then, in this order:

1. Infrastructure accounts or a rebuilt environment the buyer controls, cut over with DNS.
2. Repositories, secrets rotated, CI moved.
3. Customer contracts assigned in writing.
4. Billing platform migration and any usage metering.
5. Documentation site, domains, status page.

You mark the deal delivered with a note of what moved. The buyer confirms inside the inspection window and the money is released to you, minus 1 percent (minimum $19, maximum $199) and the card processor's fee. If they open a dispute, a person reviews the delivery evidence before anything moves.

What kills deals

• Customers who did not agree to assignment and can walk.
• A dependency on data the seller does not have rights to resell.
• Secrets embedded in customer integrations that cannot be rotated.
• No monitoring, so the buyer cannot verify uptime claims.

Questions

Do customers have to be told?

If contracts exist, usually yes, and assignment often requires consent. Plan the notice into the inspection window so the buyer can confirm the key customers stayed.

Can I keep using the API myself?

Negotiate it into the offer. Included assets and terms are part of the agreement both sides sign on Tool Index.

How is the transfer verified?

You mark delivered with a note of what moved. The buyer confirms once traffic is running on their infrastructure. Funds release only then.