Most APIs are free or subscription-based. There's a third model: pay-per-use with micropayments.

In 2026, micropayments are finally becoming practical thanks to platforms like x402. We built SLB's API with per-request micropayments. Here's what we learned.

The Problem We Solved

Support Local Businesses needs an API. Developers want to integrate our directory data into their apps, websites, and services. But charging $100–$1,000/month for API access doesn't make sense for small developers.

We wanted a model where developers pay only for what they use, small developers can use the API affordably, and we capture revenue from all usage tiers. Micropayments solve this.

How x402 Works

x402 is a micropayment network built on HTTP semantics. Here's the flow:

  1. Developer makes API request without payment
  2. Server responds with 402 Payment Required (+ pricing info)
  3. Developer sends payment proof (via x402 token)
  4. Server validates payment and serves the response

It's elegant. The developer only pays if they want the data.

Our Pricing

  • Search request: $0.001 (1/1000th of a cent)
  • Detail request: $0.0005
  • Bulk export: $0.05

These are small enough that developers don't think twice, but aggregated, they generate revenue.

Rate Limiting

Micropayments don't prevent abuse—they just make abuse expensive. We still rate-limit: 100 requests/minute per IP (free), 1,000 requests/minute per payment account (paid), and 10,000 requests/minute for enterprise accounts.

Real Outcomes

Usage breakdown:

  • 40% of requests: Free (within rate limit)
  • 45% of requests: Micropayments ($0.001–$0.01 per request)
  • 15% of requests: Enterprise contracts ($500–$5,000/month, unlimited)

Revenue impact:

  • First month: $300 in micropayments
  • Month 3: $2,000/month in micropayments
  • Month 6: $8,000/month in micropayments + enterprise contracts

Lessons Learned

  1. Pricing is delicate: $0.001 is the sweet spot. It's "I don't think about it" pricing.
  2. Free tier is essential: Allow developers to experiment before hitting the rate limit and converting to paid.
  3. Enterprise contracts matter: 90% of revenue comes from 10% of users. Offer an enterprise tier for unlimited usage.
  4. Transparency is key: Always show pricing upfront. Don't surprise developers with hidden costs.
  5. Payment provider matters: Have a backup (Stripe, Coinbase) for developers who want traditional payment methods.

Should YOU Use Micropayments?

Use micropayments if you have an API used by many small developers, usage varies widely, and your average transaction is under $1.

Don't use if you target enterprise only, need steady predictable revenue, or your users want invoices and contracts.

The Future of APIs

Micropayments are winning for APIs used by independent developers and small companies. The shift: subscription tiers → usage-based billing → micropayments.