Mesub pricing and limits

A tier belongs to a project. Its limits count across all the plans of that project, not per plan.

Change tier in the dashboard, under Plans.

A plan counts while it is live: pending, active, or sunset with an end date still ahead. A failed plan, or one past its end, takes no slot.

A subscriber is a wallet with a subscription that is active, unpaid, or cancelled and not yet past its end. A stopped subscription does not count: it takes a seat again only if it comes back, and only if there is room. A wallet subscribed to two of your plans counts once.

The dashboard shows both counts under Plans, in Project usage.

At the plan limit, a new plan cannot be published.

At the subscriber limit, a new subscription is refused with seat_cap_reached, when it is created and again when it is submitted: of several checkouts open on the last seat, one goes through. Existing subscribers are not affected.

After a downgrade, a project can hold more subscribers than its new tier allows. The seats over the limit are parked: nothing is charged on them, and their access runs to the end of the period already paid. See parked seats.

Limits are per API key, per route, per minute.

Requests with no key, or a wrong one, are counted by IP address: 120 a minute.

Every answer carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, the seconds until the window starts over. Past a limit, Mesub answers 429 rate_limited with a Retry-After header. The SDK caches access answers, so one customer checked on every request costs far fewer calls than requests.