QuotaMint

QuotaMint is a backend service for managing customer plans, feature access, usage limits, and credits inside SaaS applications. According to its website and documentation, it answers one question from your backend — can this user do this, and what does it cost? — and then writes the ledger. It is built for SaaS, AI, and API products that need to meter what customers can access and consume, and the company describes its audience as developers building SaaS, AI applications, APIs, or any software with plan-based access, credits, or usage limits. The problem QuotaMint targets is a familiar one: every usage-based SaaS eventually ends up maintaining the same infrastructure, and QuotaMint turns that infrastructure into a small API. The pieces it replaces include a credits table, usage counters, monthly resets, plan checks, feature access rules, usage limits, usage history, retry protection, and upgrade and downgrade handling. As the site puts it, a usage counter is easy, but maintaining everything around it is not. Without a service like this, plan logic becomes scattered across code, counters and credit resets have to be written by hand, retry handling is difficult, usage history is difficult to reconstruct, and the implementation becomes tied to whatever billing provider is in use. The core of the product is plan configuration. You create plans — the example on the site shows a Starter plan with 500 credits per month and a Pro plan with 2,000 credits per month — and then define what each feature costs. In the documented example, generate_text costs 1 credit, generate_image costs 10 credits, and generate_video costs 50 credits. Plans can also differ in the features they enable: you can enable or disable features for each plan, so a lower tier might have AI text and images enabled while video is disabled. Plans can define different monthly credit amounts and recurring credit allocations such as monthly credits, and the site notes that initial plans can reset on a billing cycle while more advanced rollover rules are planned. At runtime, your backend calls a single endpoint: POST /v1/consume. The request body carries a customerId, which can be any identifier you already use, a feature name, and an idempotencyKey. Every call checks the plan, the feature, and the balance, then answers allow or deny. Denied calls are described as normal answers rather than errors, so when a customer runs out of credits, consume() returns allowed: false and your application decides what to show, such as an upgrade or top-up message. QuotaMint is deliberately simple to integrate: it is plain HTTPS with no SDK and no client library required, and it works from any backend language that can make an HTTPS POST, including TypeScript, Go, Python, and Ruby. It is not a gateway: your application calls QuotaMint from the backend, and you do not need to proxy all of your traffic through it. The company states that it will not slow down your application, because it is one HTTPS POST from your backend sized to run inside your request path. Retry safety is a first-class feature. You pass an idempotency key with consume(); if the same request is retried, QuotaMint returns the original result instead of consuming again. The documented example uses a job's own identifier — never a fresh UUID per attempt — so that when a network dies, a worker crashes, or a queue redelivers a message, sending the same key returns the first answer and the customer is charged exactly once. The site illustrates this with a first request consuming 10 credits and a retry consuming 0 additional credits. Related to this, all plans include atomic credit deduction and idempotency, and every consumption creates an immutable usage record with identifiers and timestamps, making usage data auditable. Visibility is handled through the dashboard. Plans, feature costs, balances, and usage history stay visible without digging through application logs. A detailed customer view shows, for example, a customer marked ACTIVE on the Pro plan, credits remaining at 740 out of 1,000, usage this month broken down into image generations, text generations, and video generations, feature access toggles showing AI Text and Images enabled and Video disabled, and a recent usage list showing entries such as generate_image -10 and generate_text -1. Usage history answers questions about when, where, and which feature consumed credits. Plans differ in how much of this data is retained: visible usage history and audit history run 3 days on Free, 30 days on Pro, and 90 days on Scale, and usage exports are dashboard only on Free, CSV on Pro, and CSV plus JSON on Scale. QuotaMint deliberately does not replace billing. It does not process cards or collect payments, and it does not need customer passwords or card details. It works alongside Stripe, Paddle, Razorpay, Lemon Squeezy, or your existing billing setup, and it is payment-provider independent. Your application tells QuotaMint which plan a customer has — assigned, upgraded, downgraded, or removed — and the plan rules then apply. If a subscription changes, you set the customer's plan in the QuotaMint dashboard, and balances and history carry over untouched. Native billing integrations are planned, but the first release focuses on usage, credits, plans, and feature access. The company frames the boundary clearly: billing providers collect money, and QuotaMint decides what a customer can use inside your application and how much they have used. Compared with API gateways that handle routing, rate limiting, and API traffic, QuotaMint focuses on application-level usage and feature access, plans, consumption history, and allow-or-deny decisions. The overall approach is to define the rules once and call one API. The documented workflow has three steps: create your plans, define feature costs, and call consume(). This keeps product access logic in one place instead of scattered across the backend. QuotaMint sits between your billing provider and your application: payment stays with the billing provider, and runtime access decisions stay with QuotaMint. Because the check happens before the work is done, your code can ask once, and if the answer is no, nothing is charged and the application can show an upgrade prompt instead. For users, the stated outcomes are a single consume() API instead of bespoke counter code, central plan configuration, consistent feature access, credit tracking, a usage audit trail, and independence from any particular billing provider. The features people commonly rebuild — credits table, usage counters, monthly resets, plan checks, feature access rules, usage limits, usage history, retry protection, and upgrade and downgrade handling — are handled by the service, and all plans include customer plans, feature entitlements, atomic credit deduction, idempotency, API authentication, monthly grants, manual credit changes, and separate Test and Live data. QuotaMint is positioned for usage-based products and meters in the units your customers already understand: images, tokens, minutes, documents, or agent runs. Its listed use cases include AI SaaS that charges credits for images, text, video, tokens, documents, or agent runs; API products that track API usage, set usage limits, and control feature access; B2B SaaS that enables features based on plans without hard-coding plan logic everywhere; and credit-based apps that manage monthly credits, top-ups, and rollovers. It can also be used for AI token usage, tracking arbitrary units such as tokens, images, API calls, documents, storage, minutes, or custom credits. Customers can buy extra credits through credit grants or top-ups, where the billing provider handles payment and your application or a future integration updates the balance. It can even be used without credits, purely for feature access or usage limits. Pricing is per workspace and usage resets on the first day of each UTC month. The Free plan costs $0 per workspace per month and includes 5,000 events each month, one project, 60 runtime requests per minute, three days of usage history, two Test and two Live API keys per project, and one team member. Pro costs $29 per workspace per month with 2,000,000 events each month, five projects, 600 runtime requests per minute, 30 days of usage history, 10 Test and 10 Live API keys per project, and five team members. Scale costs $79 per workspace per month with 10,000,000 events each month, no project cap, 3,000 runtime requests per minute, 90 days of usage history, unlimited Test and Live API keys, and 20 team members. Every plan runs the same checks, consumption, credits, idempotency, and Test/Live isolation; upgrades only add capacity. An early-bird offer, code LAUNCH50, gives 50% off the first paid billing period, with renewals billed at the listed monthly price. Every project ships with separate Test and Live environments, so teams develop against Test keys and then flip to Live keys in production. Metadata limits per event (2 KB on Free, 8 KB on Pro, 32 KB on Scale) and metadata keys (10, 30, and 100) also vary by plan. When QuotaMint is temporarily unavailable, the backend decides: retry with the same idempotency key, which is safe, or fail open or closed for critical checks, with retry and caching guidance in the API documentation. Taken together, QuotaMint's value proposition is straightforward: stop maintaining usage logic yourself and add credits, plans, feature access, and usage limits to your SaaS with one API, while keeping your existing billing provider and the customer identifiers you already use.