How to Price an API: A Bootstrapped Founder's Guide (2026)

Short answer: Price an API on what one successful call is worth to the customer, then check it against what it costs you. Choose one billable unit, work out your cost per 1,000 units, give developers a small free tier with hard limits, and sell three monthly plans with included usage and a published overage rate. That model is easy to explain, easy to bill and hard to lose money on.

Every vendor price below was checked on the vendor's own page on 9 Nov 2026. The worked examples and the sample price sheet are ours and are labelled as such.

TL;DR#

• One billable unit. A search, a lookup, an email, a render. SerpApi says "Only successful searches are counted toward your monthly searches" (SerpApi pricing), which is a good default.
• Cost first, then value. Know your cost per 1,000 units, but set the price from the value of the result. Published prices per 1,000 units range from about $0.17 (IPinfo Core) to $25 (SerpApi Starter).
• Default model: monthly plan + included usage + overage. IPinfo and Resend both use it.
• Protect both sides: rate limits on free plans, alerts and spend caps on paid ones.
• Billing tools: Stripe Billing is 0.7% of billing volume on pay as you go (Stripe Billing pricing); Zuplo has a free plan with API keys and monetization built in (Zuplo pricing).

Disclosure: ZeroRaised is a launch site for bootstrapped products. We have no commercial relationship with any vendor named here and earn nothing if you use them. Facts come from the linked sources as checked on 9 Nov 2026.

This post covers the numbers on an API's pricing page. For the general case for metered pricing, see our guide to usage-based pricing for bootstrapped SaaS; for getting developers to try the API, see how to market an API.

Step 1: Pick the billable unit#

The billable unit is the thing you count and charge for. For an API, it should be:

• Something the customer can predict. "Lookups" or "emails sent" are easy to forecast. "Compute seconds" are not, unless your customers are infrastructure engineers.
• Tied to value. A customer is happy to pay for a search result they used. They are less happy to pay for a timeout.
• Countable on your side without argument. Log it at the gateway or in your handler, with an idempotency key, so retries do not double count.

When some calls are much more expensive than others, you have two choices. Price them as separate units, or use weighted credits. ScrapingBee does the second: JavaScript rendering costs 5 API credits per successful request, and premium proxies cost "10 or 25 credits depending on JS rendering" (ScrapingBee pricing).

Our read: credits are flexible, but every multiplier is one more thing a buyer has to work out. Start with one unit. Add weights only when a single feature costs you several times more than a normal call.

Step 2: Work out your cost per 1,000 units#

You cannot set a floor without knowing your unit cost. Here is a worked cost-plus example for a hypothetical screenshot API. All figures are illustrative assumptions, not vendor quotes, except the Stripe rates, which are from Stripe's US pricing and Stripe Billing pricing.

Then add payment costs, which hit every invoice. Stripe charges 2.9% + 30¢ per successful domestic card transaction, and Stripe Billing on pay as you go adds 0.7% of billing volume. On a $19 invoice that is $0.85 + $0.13, so about $0.98 (our arithmetic).

Now set a floor. If you want at least 70% gross margin on usage, the overage price must be at least $0.50 / 0.30 = about $1.67 per 1,000 screenshots before fees. We round up to $2 or more for small plans.

Fixed costs (monitoring, gateway, support time) are why tiny plans need a minimum price, not just a per-unit rate.

Step 3: Benchmark against real API price pages#

Cost gives you a floor. The market gives you a range. These are published prices from five APIs, checked on 9 Nov 2026. The "per 1,000" column is our arithmetic from each entry plan.

Our read: that is a 100x spread, set by what each result saves the buyer rather than by server cost. Find the two or three APIs closest to your output, not your stack. If your API replaces something a customer would otherwise do by hand or pay a person for, you can sit well above infrastructure-style prices. If you are a thin wrapper over a commodity, you will be compared with the cheapest line in this table.

Step 4: Choose a pricing model#

Two details from those pages worth copying. IPinfo's FAQ says "Overages are billed monthly at your plan's overage rate, prorated per request and rounded to the nearest $0.01." ScrapingBee says credits are "valid for one month and don't roll over." Whatever rules you choose, write them on the pricing page in one sentence each.

Our read: start with plan + included usage + overage. It gives you a predictable base and does not punish growth.

Step 5: Size the free tier#

A free tier exists to let a developer build and test an integration. It should not run a production workload.

• Cost it per account. In our screenshot example, 100 free screenshots a month cost $0.05 per account, so 1,000 free accounts cost about $50 a month (illustrative).
• Add a rate limit as well as a monthly cap. Resend limits its free plan to 100 emails per day; OpenWeather's free tier is 60 calls per minute.
• Decide what happens at the limit. Zuplo's FAQ says "On the Free tier, requests beyond your limit will be rate-limited until the next billing cycle" (Zuplo pricing). A hard stop like that means a free user never creates a bill.
• No card, if you can afford it. ScrapingBee and IPinfo Lite both advertise no card required. If abuse becomes a cost problem, tighten signup rather than shrinking the tier to nothing.

Step 6: Rate limits, alerts and spend caps#

Paid customers fear a runaway loop turning into a huge invoice. Remove that fear:

1. Rate limits per plan. SerpApi publishes throughput per hour on every plan (50 per hour on Free, 200 on Starter). Publish yours too.
2. Usage alerts at 50%, 80% and 100% of the allowance, by email and in a response header.
3. A spend cap the customer sets. Let them choose: stop at the allowance, or allow overage up to $X.
4. Bill only successful calls, and say so. It ends most billing disputes before they start.
5. A refund rule for mistakes. SerpApi offers "a full refund within 7 days of the date you subscribed to a plan unless you've used more than 20% of your searches." A clear rule like that beats ad hoc goodwill.

Step 7: Pick metering and billing tools#

You need two things: something that counts calls, and something that turns counts into invoices. Prices checked 9 Nov 2026.

Payment processing is separate: Stripe's standard US card rate is 2.9% + 30¢ per successful domestic card transaction (Stripe US pricing).

Our read: count calls in your own database or gateway, report usage to Stripe meters, and bill with Stripe Billing. If you also need API keys, rate limits and a developer portal, Zuplo's free plan covers a lot in one place. Move to a dedicated metering platform when your contracts get custom.

Sample price sheet (ours, hypothetical)#

This is the screenshot API from Step 2, priced with the steps above. It is an example, not a recommendation for your numbers.

Our arithmetic at full usage, with the $0.50 per 1,000 cost from Step 2 and Stripe at 2.9% + 30¢ plus 0.7% Billing:

• Starter: $19 revenue, $2.50 usage cost, about $0.98 fees, so about $15.52 gross profit (about 82%).
• Scale: $249 revenue, $60 usage cost, about $9.26 fees, so about $179.74 gross profit (about 72%).

The effective price per 1,000 falls from $3.80 on Starter to about $2.08 on Scale, which rewards growth without going below the margin floor. Overage on every plan stays at least three times the variable cost.

Annual plans and committed volume#

Annual plans help a bootstrapped API most with cash flow: a year paid up front funds months of runway. IPinfo's FAQ, for example, offers "yearly subscription plans for additional savings" alongside month to month billing. Our read: two months free (about 17%, our arithmetic) is an easy shape to explain. For bigger customers, a committed annual minimum in return for a lower unit rate works too. Our read: only offer it once you have that customer's usage data.

Changing prices later#

You will get your first price wrong, and that is fine. Raise prices for new signups first and watch conversion, then give existing customers clear notice with the reason and the date, and consider keeping them on their old plan for a period. Never change how a unit is counted without notice; that feels like a hidden price rise. Our guide on how to raise prices without losing customers walks through the notice emails and the grandfathering choices.

Mistakes to avoid#

• Pricing from cost alone. A 10x markup on a cheap call can still be far below what the result is worth.
• Billing failed calls. Count successful responses only, and say so on the pricing page.
• Hiding prices behind "contact us". Developers want to self-serve. Keep "contact us" for enterprise only.
• A free tier with no rate limit. One scraper can burn your monthly margin in an afternoon.
• Forgetting payment fees on small plans. The 30¢ fixed fee is a bigger share of a $5 plan than of a $49 one.

Frequently asked questions#

How do I price an API as a solo developer?#

Pick one billable unit, calculate your cost per 1,000 units including payment fees, check what comparable APIs charge, then set a free tier and three monthly plans with included usage and an overage rate. Aim for a healthy gross margin at full usage on every plan, and publish the prices on your site.

Should an API charge per call or by subscription?#

For most bootstrapped APIs, use both: a monthly subscription with an included allowance plus a published overage rate. Pure pay-per-call is simplest to understand but gives you unpredictable revenue. Pure subscriptions with no overage either cap your customers or leave you exposed to heavy users.

How big should an API free tier be?#

Big enough for a developer to build and test an integration, small enough that a free account cannot run a production workload. Published examples checked on 9 Nov 2026 include 250 searches a month on SerpApi, 1,000 credits on ScrapingBee and 3,000 emails a month on Resend. Cost your free tier per account and add rate limits.

What tools can I use to bill API usage?#

Stripe Billing charges 0.7% of billing volume on pay as you go, and Stripe's billing pricing page says basic usage billing via the Meters API includes up to 100M events per month. Metronome Starter is 0.8% of billing volume plus $0.04 per 1,000 ingest events. Orb charges $6 per credit. Zuplo combines an API gateway with monetization and has a free plan. Lago and OpenMeter did not publish prices when we checked.

How do I change my API prices later?#

Give existing customers notice, explain what changed, and consider keeping current customers on their old price for a period. Raise the price for new customers first, watch conversion, then migrate older plans. Our guide on raising prices without losing customers covers the steps.

Launch your API#

ZeroRaised is a launch directory for products built without institutional VC. Once your pricing page is live, submit your API for free and put it in front of makers who build with APIs. For more guides on pricing and growing without investors, join the ZeroRaised newsletter.

Sources#

• Stripe US pricing, last checked 9 Nov 2026
• Stripe Billing pricing, last checked 9 Nov 2026
• Metronome pricing, last checked 9 Nov 2026
• Orb pricing, last checked 9 Nov 2026
• Zuplo pricing, last checked 9 Nov 2026
• Lago pricing, last checked 9 Nov 2026
• OpenMeter pricing, last checked 9 Nov 2026
• ScrapingBee pricing, last checked 9 Nov 2026
• SerpApi pricing, last checked 9 Nov 2026
• IPinfo pricing, last checked 9 Nov 2026
• Resend pricing, last checked 9 Nov 2026
• OpenWeather pricing, last checked 9 Nov 2026