How To Price AI Agent Usage

Fastest Working Method

1. Estimate p50 and p90 cost per active user/month under realistic workflow assumptions.
2. Pick a candidate monthly price and target gross margin.
3. Check whether both blended cost and p90 cost fit under the margin target.
4. Choose the lightest policy that protects margin without making the offer hard to buy.

Choose the Pricing Policy

• Use a flat plan when p90 usage is close to p50 usage and AI cost is small relative to price.
• Use included credits or allowances when buyers want predictable pricing but usage varies by customer.
• Use usage caps when the buyer wants flat pricing but the product needs a hard margin boundary.
• Use top-ups, usage pricing, or per-customer metering when expensive workflows are obvious and customers understand the meter.
• Use outcome pricing only when the outcome is consistent enough that cost and value can be measured together.

Pricing Ladder Example

A candidate $49/month plan can look healthy if typical users cost $8/month. At an 80% margin target, the typical-user price floor is $40, so the flat plan appears to work.

But if 10% of users cost $80/month, blended cost becomes $15.20 and the 80% margin price floor becomes $76. The same $49 plan now needs a monthly allowance, credit burn, top-up, or workflow cap before heavy users silently erase margin.

Stripe Boundary

• Let Stripe handle subscriptions, invoices, renewals, and paid top-ups.
• Keep the source-of-truth usage ledger in the product, because it knows workflow, model, account, and snapshot context.
• Use webhooks to add plan allowance or purchased credits, then decrement credits from the internal ledger as work runs.
• Do not expose raw token math to customers unless the buyer already expects usage-based infrastructure pricing.

Minimum Ledger Fields

• Account or customer id, plan id, and billing period.
• Workflow id, model/provider route, request count, and input/output token totals.
• Internal provider cost, customer-facing credit delta, and pricing snapshot id.
• Timestamp and idempotency key for billing and retry safety.

Pricing Mistakes To Avoid

• Using the average user only, then discovering p90 users are negative-margin.
• Letting the billing meter become the cost ledger instead of keeping workflow economics in the app.
• Calling the plan unlimited when the product already has expensive premium routes.
• Hiding every expensive workflow under one flat tier before usage has settled.