Skip to content

API usage billing that matches every call

With API usage billing, customers pay for the requests they make. Payrudder counts each call once and prices it per unit, by tier or by package. Quota checks are fast enough to sit in your request path.

The hard part

  • 01

    Millions of small events arrive, and retries must not count twice

  • 02

    Tiered prices are easy to describe and hard to calculate right

  • 03

    Quotas have to be checked on every request without slowing it down

How Payrudder handles it

  1. Idempotent ingest in batches of 500

    A repeated idempotency key comes back as a duplicate and is not counted again. Once an event is accepted, it is not lost.

    Idempotent ingest in batches of 500
  2. Per unit, tiered or package

    Price calls per unit, with graduated tiers or in packages, plus a fixed monthly fee if you want one.

    Per unit, tiered or package
  3. Quotas in milliseconds

    Entitlement checks read from Redis counters. The counters are reconciled with the authoritative totals at regular intervals.

    Quotas in milliseconds

Questions

How many events can it take?

On a laptop with a 2.9 GiB Docker VM it sustained 5,000 events per second at p99 32 ms with no errors. Server hardware does better. The benchmark report covers the method and the targets it missed.

Can I give a free tier?

Yes. Graduated tiers can start with a free first tier, for example the first 10,000 calls.

Start billing by usage

The free plan covers your first live payments. Hook up one meter, close a month in test mode, then go live.