Pricing overview - Unprice Documentation

For usage-based products, pricing is a runtime decision and an evidence trail. The important moment is not only the invoice. It is the paid action in your product: an API request, LLM call, workflow, data job, export, or tool run that can create cost before billing catches up. Unprice connects that action to one customer money path:

paid action -> plan version -> pricing rule -> meter -> entitlement -> budget -> wallet -> invoice evidence

Core model

Concept	What it does	Why it matters
Plan	Commercial package your team sells	Groups features into an offer
Plan version	Published snapshot of pricing and entitlement rules	Keeps existing customers on the pricing they bought
Feature	Sellable or gateable product capability	Gives your app a stable slug to check
Meter	Rule that turns events into usage	Powers usage limits, spend, and invoice evidence
Entitlement	Customer’s right or limit for a feature	Lets your app check what the customer can do
Budget	Customer or workload spend cap	Stops over-budget work before it runs
Wallet credit	Spend balance held for a customer	Separates money/credits from entitlement grants
Invoice evidence	Trail from decision to charge	Explains billed usage and credits; denied usage creates no invoice line

Runtime calls

Use these calls inside your product:

access.check asks whether a customer can use a feature without changing state.
usage.consume synchronously applies known usage and returns the allow or deny decision.
usage.record asynchronously reports usage for metering and evidence.
runs.start, runs.consume, and runs.end reserve and consume a budget for multi-step work.

Read Choose the runtime call before wiring production enforcement.

Next steps

Plans and versions

Learn how plans and immutable versions keep pricing changes safe.

Usage metering

Learn how events become period-scoped usage.