# QuotaMint An API for managing customer plans, feature access, credits, and usage tracking while keeping billing with your existing provider or custom system. Helps usage-based SaaS and API products make runtime access decisions and record consumption. - Findings24: - Website: - Pricing: Freemium - Categories: AI Developer Tools ## What is QuotaMint? QuotaMint is an application-level API for customer plans, feature access, credits, and usage tracking. A backend asks whether a customer can use a feature and what it costs; QuotaMint checks the plan and balance, returns an allow-or-deny decision, and records the consumption. It works alongside existing billing rather than replacing it. Teams keep their payment provider or custom billing system, while QuotaMint centralizes runtime access rules, balances, usage history, and retry-safe consumption for usage-based products. ## What can QuotaMint do? ### Plan and feature checks Define customer plans and feature costs in one place. Each consume request checks the customer’s plan, whether the feature is available, and whether the balance covers the requested action. ### Credit and usage ledger Record consumption and keep balances, usage history, and counters available for inspection instead of maintaining separate application tables and logs. ### Idempotent consumption Pass a stable idempotency key with a request so retries return the original result without consuming credits a second time. ### Bring-your-own billing Continue using Stripe, Paddle, Razorpay, Lemon Squeezy, or a custom billing system. The application tells QuotaMint which plan a customer has, while payment collection remains with the billing provider. ### Centralized access configuration Manage plans, feature costs, customer balances, and feature access in a dedicated dashboard, keeping product access logic out of scattered backend code. ### Plain HTTPS API Call the service directly over HTTPS without an SDK or client library. The documented example uses a bearer key and the POST \`/v1/consume\` endpoint. ## Use Cases ### AI generation products Meter image, text, video, token, document, or agent-run features with different credit costs and deny a request when the customer has insufficient balance. ### Usage-based API products Apply plan-specific usage limits and feature access checks before processing API work, while recording each accepted consumption in a central ledger. ### B2B SaaS plan entitlements Enable or disable product capabilities by customer plan without duplicating plan-condition logic throughout the application backend. ### Retry-prone background jobs Use a stable job identifier as the idempotency key when workers or queues may retry a request, preventing the same operation from consuming credits twice. ### Products with existing billing Keep subscription and payment workflows in an established billing system, then synchronize the customer’s plan to QuotaMint for runtime usage decisions and credit tracking. ## Frequently Asked Questions ### Does QuotaMint replace Stripe or another billing provider? No. QuotaMint is designed to complement billing systems. The site says customers can keep Stripe, Paddle, Razorpay, Lemon Squeezy, or custom billing, while QuotaMint handles runtime access, credits, and usage tracking. ### How does a consumption check work? The backend sends a customer ID and feature to \`POST /v1/consume\`, optionally with an idempotency key. QuotaMint checks the plan, feature access, and balance, then returns an allow-or-deny result and records an allowed consumption. ### What happens when a request is denied? A denied call is presented as a normal decision rather than a service error. The example shows the application returning a 402 response with an “Out of credits” message without charging the customer. ### How does QuotaMint prevent double charging on retries? The caller supplies the same stable idempotency key when retrying the same operation. QuotaMint returns the original result and does not consume the credits again. ### Who is QuotaMint intended for? The site describes it for AI SaaS, usage-based API products, B2B SaaS, and credit-based applications that need plan checks, feature access, or metered consumption. ## Quick Facts - **Category**: Usage metering and feature-access API - **Primary users**: AI SaaS, API products, B2B SaaS, and credit-based applications - **API workflow**: HTTPS POST to \`/v1/consume\` with a customer ID, feature, and optional idempotency key - **Billing model**: Bring your own billing provider or custom billing system - **Metering examples**: Images, text, video, tokens, minutes, documents, and agent runs - **Pricing structure**: Workspace-based plans with Free, Pro, and Scale tiers shown on the product site