Skip to main content
Valqio

Use cases

Turn your pricing model into product behavior.

From AI generations and paid API calls to seat changes and long-running jobs, Valqio applies plans, credits, limits, and reservations before each product action runs.

Find your patternTry the playground

Start with the work you sell.

Shared mechanism

Different offers. One way to decide what runs.

  1. 01Define

    Define plans, credits, limits, and reservation rules.

  2. 02Call

    Send the customer, action type, and quantity before the action starts.

  3. 03Decide or reserve

    Allow or block the action now, or reserve credits until it finishes.

  4. 04Settle if needed

    Commit successful usage or release the reservation after failure.

  5. 05Inspect

    See why the action ran and what changed afterward.

Shared runtime

See the decision before the action.

Each example asks whether this customer can run this product action now.

Runtime decision Allowed
AI generation requestimage.generate

acme-production · Growth AI · quantity 1

  1. 01Plan resolvedGrowth AI
  2. 02Credits checked20 required · 100 available
  3. 03Policy evaluatedpremium-model · enabled
  4. 04Evidence readydecision · inputs · usage
Provider work can beginAllow
API credit check Allowed
499 credits remaining

1 call accepted · usage attached

Plan assignment Effective
Account
acme-inc
Plan
Growth
Override
+25 seats

Effective package resolved

Job reservation Held

Reserve Run job Commit

Capacity protected while work is in flight.

Meet each product where its value is created.

01

AI products

Stop costly requests before provider work.

For AI product teams shipping agents, copilots, or generation features.

When
When a customer starts an AI generation, agent run, or premium-model request.
Benefit
Check the customer's plan and credit balance before the provider call. Reuse the idempotency key so retries do not deduct credits twice.
Proof
The decision record shows the action, plan, credits checked, outcome, and usage recorded afterward.
Generation gateReady
POST/v1/images/generate
  1. Entitlement activepremium.image
  2. Credits available100 available · 20 required
  3. Product workmay begin after allow
Decision ALLOWED
02

APIs & data

Sell credits and paid API usage.

For teams monetizing endpoints, data access, or developer operations.

When
When a customer calls a paid API endpoint or starts a metered data export.
Benefit
Check the credit balance or contracted limit before the call runs, then record accepted usage once even when the client retries.
Proof
The decision record links the API action, balance change, idempotency key, and resulting usage event.
Developer walletacme-dev
Available balance499 credits
Nowapi.search−1
Earlierapi.export−5
Grantmonthly allocation+500
Decision and usage share one reference
03

SaaS packaging

Keep plans, seats, and overrides out of route code.

For SaaS teams with packaging that changes faster than application routes.

When
When a customer invites a seat, runs an advanced export, or uses an add-on.
Benefit
Resolve the plan, seat count, and customer override before the action runs. A blocked retry leaves the account state unchanged.
Proof
The decision record shows the effective package, override, action outcome, and policy version used.
Effective packageGrowth · v15
Accountacme-inc
Effective now
FeatureAI agentsEnabled
LimitSeats75
IncludedCredits12M
04

Compute & workflows

Reserve scarce value and capacity.

For products that start long-running or failure-prone work.

When
When a customer starts a render, export, or other long-running job.
Benefit
Reserve credits before the job starts, commit successful usage once, and release the reservation after failure or cancellation.
Proof
The usage transaction shows the reservation, job outcome, commit or release, and remaining balance.
Reservation lifecyclejob_8K21
  1. 1
    Reserved40 compute credits held
  2. 2
    Work in flightValue is protected
  3. 3
    Commit or releaseResolve from the job outcome
Available 460Reserved 40Total 500

Decision evidence

One decision record. Built for engineering and support.

Inspect the commercial context used at runtime without reconstructing it from application logs.

The same explanation can travel from a production incident to a customer answer.
Decision record Allowed
Subject
acme-production
Action
image.generate
Commercial model
Growth AI · credit wallet
Decision
Allowed
Evidence
Plan, balance, quantity, policy version
Usage
1 accepted generation
Trace refdec_01JQ8VALQIOEvidence available

Who it helps

Used across teams

One runtime record answers a different practical question for each role.

  • Technical founders

    Launch a commercial model without turning it into permanent route logic.

  • Backend / platform engineering

    Give every service a consistent enforcement call and an inspectable decision record.

  • Product / pricing

    Change packages and limits without coordinating a deployment for every edit.

  • Support / operations

    Answer why work ran or stopped from the same evidence the runtime used.

A clear boundary

Valqio decides product behavior. Your billing provider handles invoices and payment.

Keep the runtime decision close to the product action, and keep invoicing where it already belongs.

Runtime monetization

Stop hardcoding how your product monetizes.

Define the offer once. Apply it before each product action runs.

Create a free SandboxExplore the playground