Skip to main content
Unprice sits between your product, the paid work that your customer starts, and your payment provider. Your application owns the product experience and workload execution. Your payment provider captures payment. Unprice owns the customer money path between them: pricing rules, entitlement decisions, usage evidence, wallet credits, billing state, and the trail that explains why work was allowed, denied, or billed.
A paid action passes through plan version, entitlement, budget, and wallet checks. Unprice allows or denies the action before work runs and preserves invoice evidence.

The request-to-invoice money path

​
The three boundaries

Your product

Runs the user experience and workload. It decides when a paid action is about to run.

Unprice

Resolves pricing rules, entitlement decisions, budgets, wallet credits, billing state, and evidence.

Payment provider

Captures payment through Stripe or simulates payment in Sandbox.

​
The money path

​
The payment-provider boundary

Unprice is not a Stripe wrapper. Stripe is the production provider today, and Sandbox is available for testing. The provider interface separates invoice creation, payment methods, checkout and setup sessions, payment collection, and webhooks from pricing and entitlement logic. This separation lets Unprice keep the pricing and evidence path when the payment-capture system changes. The provider model can support another provider without moving entitlement, metering, wallet, billing, or invoice-evidence logic into product code.

​
The runtime paths

Ask without changing state

Use access.check when your app only needs to know whether a customer can use a feature.

Decide and apply now

Use usage.consume when known usage must be denied after a limit, budget, or credit balance is exhausted.

Report usage evidence

Use usage.record when the request does not wait for Unprice to decide.

Reserve a workload budget

Use runs.start, runs.consume, and runs.end for jobs, workflows, tool chains, and agents.

​
What Unprice does not own

Unprice does not run your product workload. Your application still calls the LLM, starts the job, sends the API request, or runs the workflow. Unprice also does not replace your payment provider. Stripe captures payment and Sandbox simulates payment for testing. Unprice keeps the pricing logic and evidence path that explains what should be charged, credited, denied, or replayed.