01
Create your plans
Starter500 credits / month
Pro2,000 credits / month
Credits + usage limits + feature access
Stop rebuilding credits and usage limits.
QuotaMint answers one question from your backend — can this user do this, and what does it cost? — then writes the ledger. You keep Stripe. We keep count.
Early-bird offer for launch customers — claim it before it ends
charge-user.ts
// before you do the work, ask once
const decision = await fetch(process.env.QUOTAMINT_URL + "/v1/consume", {
method: "POST",
headers: { Authorization: "Bearer " + process.env.QUOTAMINT_KEY },
body: JSON.stringify({
customerId: "user_123", // any id you already use
feature: "generate_image", // priced when you set up the plan
idempotencyKey: "job_8472", // same key on retry: charged once, ever
}),
});
const { allowed } = await decision.json();
if (!allowed) {
// nothing was charged. show an upgrade prompt instead.
return res.status(402).json({ error: "Out of credits" });
}Plain HTTPS. No SDK, no client library.
The familiar problem
You’ve probably built this before.
Every usage-based SaaS eventually ends up maintaining the same infrastructure. QuotaMint turns that into a small API.
Credits table
Usage counters
Monthly resets
Plan checks
Feature access rules
Usage limits
Usage history
Retry protection
Upgrade and downgrade handling
How it works
Define the rules once. Call one API.
QuotaMint keeps product access logic in one place instead of scattered across your backend.
02
Define feature costs
generate_text1 credit
generate_image10 credits
generate_video50 credits
03
Call consume()
POST /v1/consume
{ "customerId": "user_123",
"feature": "generate_image" }Every call checks the plan, the feature, and the balance — then answers allow or deny. Denied calls are normal answers, not errors.
See the whole customer
Configure access. Inspect every credit.
Plans, feature costs, balances, and usage history stay visible without digging through application logs.
Acme Inc.
user_123
ACTIVEPlan · Pro
Credits remaining
740740 / 1,000
Usage this month
Image generations26
Text generations84
Video generations2
Feature access
AI TextEnabled
ImagesEnabled
VideoDisabled
Recent usage
generate_image-10
generate_text-1
generate_image-10
Bring your own billing
Keep your existing billing.
QuotaMint doesn’t replace Stripe, Paddle, Razorpay, Lemon Squeezy, or your billing system.
Your app tells QuotaMint which plan a customer has. QuotaMint handles everything after that.
Subscription changed? Upgrade, downgrade, or cancel — you set the customer’s plan in the QuotaMint dashboard. Balances and history carry over untouched.
Native billing integrations are planned later.
Stripe / Paddle / Razorpay / Custom Billing
Customer plan
QuotaMint
Credits + usage + access
Your application
Payment stays with your billing provider. Runtime access decisions stay with QuotaMint.
Built for usage-based products
One API, whatever you sell.
Images, tokens, minutes, documents, agent runs — meter it in the units your customers already understand.
AI SaaS
Charge credits for images, text, video, tokens, documents, or agent runs.
API products
Track API usage, set usage limits, and control feature access.
B2B SaaS
Enable features based on plans without hard-coding plan logic everywhere.
Credit-based apps
Manage monthly credits, top-ups, rollovers, and consumption.
Safe consumption
Retries don’t double-charge usage.
Pass an idempotency key with consume(). If the same request is retried, QuotaMint returns the original result instead of consuming again.
Idempotent consumption by design.
image-job.ts
// the job's own id — never a fresh uuid per attempt
await fetch(process.env.QUOTAMINT_URL + "/v1/consume", {
method: "POST",
headers: { Authorization: "Bearer " + process.env.QUOTAMINT_KEY },
body: JSON.stringify({
customerId: "user_123",
feature: "generate_image",
idempotencyKey: "image_job_8392", // stable across retries
}),
});
// network died? worker crashed? queue redelivered?
// send the SAME key again — you get the first answer back
// and the customer is charged exactly once.First request
-10 credits
Retry
0 additional credits
Why QuotaMint
Keep product rules out of your product code.
A usage counter is easy. Maintaining everything around it is not.
Without QuotaMint
- –Plan logic scattered across code
- –Custom counters
- –Custom credit resets
- –Difficult retry handling
- –Difficult usage history
- –Billing-provider-specific logic
With QuotaMint
- One consume() API
- Central plan configuration
- Consistent feature access
- Credit tracking
- Usage audit trail
- Billing-provider independent
The infrastructure boundary
QuotaMint complements payments. It doesn’t replace them.
Billing providers collect money. QuotaMint decides what a customer can use inside your application.
| Product category | Primary responsibility | Where QuotaMint fits |
|---|---|---|
| Stripe / Paddle | Payments, subscriptions, and invoices | Usage, credits, feature access, and runtime decisions |
| API gateways | Routing, rate limiting, and API traffic | Application-level usage and feature access |
| QuotaMint | Complements billing and gateway infrastructure | Plans, consumption history, and allow or deny decisions |
Pricing
Choose capacity, not a different integration.
Every plan runs the same checks, consumption, credits, idempotency, and Test/Live isolation. Upgrade only when your traffic or team needs more room.
Prices are per workspace. Usage resets on the first day of each UTC month.
Get 50% off your first paid billing period with LAUNCH50. Enter the code at checkout; renewals are billed at the listed monthly price. Available for a limited time.
Free
Ship one product with the complete metering core.
$0per workspace / month
- 5,000 events each month
- 1 project
- 60 runtime requests / minute
- 3 days of usage history
- 2 Test + 2 Live API keys per project
- 1 team member
Pro
Run several products with exports and team controls.
$29per workspace / month
- 2,000,000 events each month
- 5 projects
- 600 runtime requests / minute
- 30 days of usage history
- 10 Test + 10 Live API keys per project
- 5 team members
Scale
Support higher traffic, larger teams, and longer history.
$79per workspace / month
- 10,000,000 events each month
- No project cap
- 3,000 runtime requests / minute
- 90 days of usage history
- Unlimited Test and Live API keys
- 20 team members
Compare every limit
Runtime capacity, data retention, and team controls are enforced from the same plan definition used by the product.
Free$0 per month
Capacity
- Projects
- 1
- Workspaces
- 1
- Monthly events
- 5,000
- Active API keys — Test
- 2
- Active API keys — Live
- 2
- Team members
- 1
Runtime
- Requests per minute
- 60
- Metadata per event
- 2 KB
- Metadata keys
- 10
- Visible usage history
- 3 days
- Audit history
- 3 days
Operations
- Usage exports
- Dashboard only
- Project roles
- Workspace roles
- Credit top-ups
- Basic
Pro$29 per month
Capacity
- Projects
- 5
- Workspaces
- 5
- Monthly events
- 2,000,000
- Active API keys — Test
- 10
- Active API keys — Live
- 10
- Team members
- 5
Runtime
- Requests per minute
- 600
- Metadata per event
- 8 KB
- Metadata keys
- 30
- Visible usage history
- 30 days
- Audit history
- 30 days
Operations
- Usage exports
- CSV
- Project roles
- Admin and developer
- Credit top-ups
- Standard
Scale$79 per month
Capacity
- Projects
- No cap
- Workspaces
- 10
- Monthly events
- 10,000,000
- Active API keys — Test
- No cap
- Active API keys — Live
- No cap
- Team members
- 20
Runtime
- Requests per minute
- 3,000
- Metadata per event
- 32 KB
- Metadata keys
- 100
- Visible usage history
- 90 days
- Audit history
- 90 days
Operations
- Usage exports
- CSV + JSON
- Project roles
- Admin, developer, viewer
- Credit top-ups
- Standard
| Plan capability | Free$0 / month | Pro$29 / month | Scale$79 / month |
|---|---|---|---|
| Capacity | |||
| Projects | 1 | 5 | No cap |
| Workspaces | 1 | 5 | 10 |
| Monthly events | 5,000 | 2,000,000 | 10,000,000 |
| Active API keys — Test | 2 | 10 | No cap |
| Active API keys — Live | 2 | 10 | No cap |
| Team members | 1 | 5 | 20 |
| Runtime | |||
| Requests per minute | 60 | 600 | 3,000 |
| Metadata per event | 2 KB | 8 KB | 32 KB |
| Metadata keys | 10 | 30 | 100 |
| Visible usage history | 3 days | 30 days | 90 days |
| Audit history | 3 days | 30 days | 90 days |
| Operations | |||
| Usage exports | Dashboard only | CSV | CSV + JSON |
| Project roles | Workspace roles | Admin and developer | Admin, developer, viewer |
| Credit top-ups | Basic | Standard | Standard |
All plans include customer plans, feature entitlements, atomic credit deduction, idempotency, API authentication, monthly grants, manual credit changes, and separate Test and Live data. Active API key limits apply per project and per environment: Test and Live keys are counted separately.
Frequently asked questions
Everything developers ask before adding QuotaMint.
Documented behavior, real limits, and clear boundaries.
What is QuotaMint?
QuotaMint is a backend service for managing customer plans, feature access, usage limits, and credits in SaaS applications.
Is QuotaMint a payment gateway?
No. QuotaMint does not process cards or collect payments. Continue using Stripe, Paddle, Razorpay, Lemon Squeezy, or your own billing system.
How does QuotaMint know which plan a customer is on?
Your application tells QuotaMint when a customer gets a plan — assigned, upgraded, downgraded, or removed. After that, the plan rules just apply.
Do I need Stripe?
No. QuotaMint is payment-provider independent.
Can I use Paddle, Razorpay, or Lemon Squeezy?
Yes. Sync the customer’s plan from any provider — QuotaMint doesn’t care where the money came from.
Will native Stripe integration be available?
Native billing integrations are planned, but the first release focuses on usage, credits, plans, and feature access.
What happens when a customer uses a feature?
Your backend calls consume(). QuotaMint checks the customer’s plan, feature access, credit cost, and remaining balance, then returns whether the action is allowed.
Can different features cost different amounts?
Yes. For example, text generation can cost 1 credit, image generation 10 credits, and video generation 50 credits.
Can plans have different feature access?
Yes. You can enable or disable features for each plan.
Can plans have different monthly credit amounts?
Yes. For example, Starter can have 500 credits and Pro can have 2,000 credits.
What happens when credits run out?
consume() returns allowed: false and your application decides what to show, such as an upgrade or top-up message.
How are retries handled?
QuotaMint supports idempotency keys. Repeating the same consume request with the same idempotency key will not consume usage twice.
Can I see why credits were consumed?
Yes. QuotaMint keeps usage history so you can see when, where, and which feature consumed credits.
Can customers buy extra credits?
Yes, through credit grants or top-ups. Your billing provider handles the payment, and your application or a future integration updates the credit balance.
Can credits reset every month?
Yes. Plans can define recurring credit allocations such as monthly credits.
Can credits roll over?
Initial plans can reset on a billing cycle. More advanced rollover rules are planned.
Does QuotaMint sit in front of my API like an API gateway?
No. Your application calls QuotaMint from the backend. You do not need to proxy all of your traffic through QuotaMint.
Will QuotaMint slow down my application?
No. It is one HTTPS POST from your backend, sized to run inside your request path.
What languages are supported?
Any backend language that can make an HTTPS POST: the REST API works unchanged from TypeScript, Go, Python, Ruby, and more.
Can I use QuotaMint for AI token usage?
Yes. You can track arbitrary usage units including tokens, images, API calls, documents, storage, minutes, or custom credits.
Can I use it without credits?
Yes. You can use QuotaMint only for feature access or usage limits if your product does not use a credit system.
Can I use it for API rate limits?
QuotaMint focuses primarily on application usage and feature-access logic. Basic usage limits can be supported, but it is not intended to replace a full API gateway.
How is QuotaMint different from Stripe?
Stripe handles payments and subscriptions. QuotaMint handles what a customer can use inside your application and how much they have used.
How is QuotaMint different from RevenueCat?
RevenueCat primarily handles mobile app purchases and feature access. QuotaMint is designed for backend SaaS, AI, and API products with usage-based features and credits.
How is QuotaMint different from Zuplo or Tyk?
Zuplo and Tyk are primarily API management and gateway products. QuotaMint does not require routing your API traffic through a gateway and focuses on application-level usage, credits, plans, and feature access.
What happens if QuotaMint is temporarily unavailable?
Your backend decides: retry with the same idempotency key (safe), or fail open or closed for critical checks. Retry and caching guidance is part of the API documentation.
Is usage data auditable?
Yes. Every consumption creates an immutable usage record with identifiers and timestamps.
Can I send my own customer ID?
Yes. QuotaMint works with the customer, user, or organization identifiers you already use.
Does QuotaMint store my customer passwords or payment details?
No. QuotaMint does not need customer passwords or card details.
Who is QuotaMint for?
Developers building SaaS, AI applications, APIs, or any software with plan-based access, credits, or usage limits.
Who is QuotaMint not for?
Teams looking for a payment processor, accounting platform, full API gateway, or complete subscription checkout system.
How do I integrate?
One HTTPS POST to the REST API from your server — no client library required. Examples use cURL and native fetch.
Can I test it before using it in production?
Yes. Every project ships with separate Test and Live environments — develop against Test keys, then flip to Live keys in production.
How much will it cost?
The Free plan is $0. Pro starts at $29 per month and Scale at $79, per workspace. Use LAUNCH50 for 50% off your first paid billing period; renewals are billed at the listed monthly price. Enter the code at checkout. Available for a limited time.
How do I get started?
Create a free account — the setup guide walks you through your first workspace, project, plan, and feature.
Now live
Stop maintaining usage logic yourself.
QuotaMint is launched. Add credits, plans, and usage limits to your SaaS with one API — starting from the free plan.
Early-bird offer for launch customers — claim it before it ends