The founders and the product
Warp built a developer product while its AI usage and underlying model costs made the relationship between usage and revenue more important.
A developer terminal and AI workflow product with usage-based billing. Warp connected developer workflows, AI usage, and usage-based billing.
How the company sells the AI product
The team added usage-based billing alongside its payment experience so that some revenue could follow actual usage.
The figures are reported by Stripe in its customer case study and do not equal profit.
What the public record shows
The case says revenue grew 150% from June to August 2024 after usage-based billing was adopted, with usage-based billing at about 20% of revenue. It also reports 23x revenue growth that year. The underlying business problem was that developers could reach the request limit in a fixed subscription but had no way to buy more credits during the billing cycle. Warp added base plans with included credits and automatic overage billing, using webhooks and API calls to meter AI requests and charge for additional usage.
Stripe says the implementation took three weeks with two engineers, and the resulting flow let developers continue working instead of rationing credits. The page also reports that 98% of transactions used Stripe Checkout and about 50% used Link; these are payment-channel metrics, not profit. Public materials do not establish that Warp uses APIToken.
The reported milestone
Stripe reports that Warp grew revenue 150% from June to August 2024 after adopting usage-based billing, which represented about 20% of revenue. The case also says revenue grew 23 times that year.
The numerical claims in this article come from the Stripe customer case study cited below.
Platform context
APIToken（https://apitoken.company/） provides a compatible API, isolated project keys, public status, usage records, and budget controls for AI application work.
The cited material does not state that Warp uses APIToken（https://apitoken.company/）.