Usage, Pricing & Credits
Everything in Model Match runs on a single currency — credits. Your plan includes a monthly allowance and you can buy more any time. This page explains the credit model — the two buckets every balance is split into, the order usage draws them down, and how charges route between you and your organization.
Almost everything you do in Model Match — every API read, every enrichment, every export — is paid for in credits. One currency, one balance, one set of rules. This page is the mental model; the pages that follow drill into how to buy credits and how to track usage.
What a credit is
A credit is the unit of usage. What a single credit is worth depends on your plan and agreement — the exact price is always shown in the purchase dialog before you buy, so there's nothing to guess at checkout.
You acquire credits two ways:
- Included with your plan — every plan grants an allowance of credits at the start of each billing cycle.
- Purchased — buy more on demand, or have them topped up automatically. Larger purchases come at a better per-credit rate (see Buying Credits).
The two buckets
Your balance isn't a single number — it's split into two buckets that behave differently:
| Bucket | Filled by | Rolls over? |
|---|---|---|
| Cycle | Your plan's monthly credit grant (and any enterprise allocation) | No — unused cycle credits expire at the start of each billing cycle |
| On-demand | Credits you buy (manually or via auto-purchase), plus refunds, gifts, and adjustments | Yes — they never expire |
In the app these appear as Included usage (your cycle bucket) and On-demand credits (your on-demand bucket) on the My credit usage page.
The distinction matters because of how usage draws them down:
Usage always spends your cycle bucket first, then your on-demand bucket. Your included monthly credits are consumed before any credits you paid for — so purchased credits act as a reserve that only gets touched once the month's allowance is used up. Anything left in the cycle bucket at the end of the period is forfeited; anything in on-demand carries forward.
Who gets charged: you vs. your organization
In Model Match, the organization owns the subscription and the payment method, but credits are allocated per member — every member of a workspace carries their own balance. When you make a call, the cost is debited from your balance within the organization, not a shared pool.
When you spend, credits are drawn in this order:
- Your organization cycle bucket
- Your organization on-demand bucket
- Your personal cycle bucket — only if you hold a personal subscription
- Your personal on-demand bucket — only if Spending beyond cycle is on for your personal pool
Steps 3 and 4 are opt-in. By default, your usage is funded entirely by your organization. If you want your own credits to cover overflow once the org balance runs dry, turn on Spending beyond cycle for your personal pool (see Personal credits). This lets a member keep working on their own dime without the org admin having to top up the whole team.
API keys spend the key owner's balance. A request authenticated with an API key (or a token) is charged to the member who owns that key, inside their organization — following the same waterfall above.
Where credits come and go
Every movement of credits is recorded as a line in your credit ledger, each tagged with a type:
| Type | What it is |
|---|---|
usage | A debit for an API call, enrichment, or export |
subscription_grant | Your monthly included credits landing in the cycle bucket |
purchase | Credits you bought manually |
auto_purchase | An automatic top-up |
gift | Credits granted to you by an admin |
transfer | Credits moved between members |
refund | Credits returned to you |
adjustment | A manual correction by an admin |
expiry | Unused cycle credits burned at the start of a new period |
You can read the full ledger and aggregate your usage on the Tracking Usage page.
Next steps
Other MCP clients
Connect any MCP-compatible application to the Model Match MCP server.
Buying Credits
Top up your balance from My credit usage. Buy credits on demand — larger purchases come at a better per-credit rate. Turn on Spending beyond cycle to keep working past your included credits, capped per billing period by your cycle cap, drawing from your workspace or personal pool.