Pay-Per-Result API Pricing Is Changing How Developers Buy Data
If you've ever signed up for a data API, you know the drill: pick a monthly tier, guess your usage, then either overpay for headroom you never touch or blow past quota on day 19. The pricing model is older than the web, and it's still everywhere.
A quieter shift has been happening on platforms where APIs and scrapers are sold as products: pay-per-result (PPE) billing. You don't pay for compute time, subscription tiers, or request counts. You pay per record you actually receive — a job listing, a profile, a review, a product.
Why Devs Prefer PPE
1. Cost maps to value. If a scraper returns 45,000 LinkedIn job postings, you pay for 45,000 rows. If it returns 42, you pay for 42. No idle months, no overage surprises.
2. Failure is free. Scraper broke because the target site shipped a redesign? You get zero results and pay zero. Try doing that with a $99/month subscription.
3. Budgeting is trivial. rows × unit_price is a spreadsheet cell, not a capacity-planning meeting. Finance teams love it.
4. No lock-in. Tier-based APIs punish you for leaving mid-cycle. PPE has no cycle.
Where You're Seeing This
Apify has been running a PPE model across its Actor marketplace, where individual scrapers set per-result prices (often $0.01–$0.10). You run a scraper, you get rows, you pay for rows. Billing is handled by the platform, so you're not chasing invoices.
I've been shipping actors there for a few months — LinkedIn Jobs, Indeed, IndieHackers, Instagram profile, Reddit — and what's become obvious is that PPE lets tiny niche scrapers exist at all. A dataset nobody needs enough to justify a $49/mo tier can still make sense at $0.02/result for the three people a week who want exactly that data.
Downsides, to Be Honest
- Price discovery is harder. You don't know what a run will cost until you estimate row counts.
- Spiky workloads can get expensive. If you need 2M rows once, a flat-tier API might be cheaper.
- Per-result pricing rewards stable, well-defined schemas. Scrapers returning blobby HTML don't fit the model.
The Takeaway
If you're buying data in 2026, default to asking "what's the per-result price?" before "what's the monthly plan?" The per-unit number tells you more about the actual economics than any marketing page.
Check out the PPE actors I maintain at apify.com/cryptosignals — job market data, social profiles, review datasets. Pay for what you pull.
Top comments (0)