RuntimeAI Monetization Runtime

Payment is not access.
Authorize before compute.

Licenzy is the runtime between commercial state and AI execution. It confirms entitlements, checks credits, and authorizes every call before compute is spent — then records the evidence to keep commercial state and execution aligned.

Built forAI foundersPlatform & infra engineersCTOs
runtime · authorization
Granted
POST/v1/access/check
›subjectcus_9f2c41
›productworkflow.summarize
›entitlementactive
›credits1,204
›commercial statesynced
authorize before computeGranted
evt_9f2c41 · idempotentauthorized in 41ms
01The gap

A successful payment is not the same as valid application access.

Between the moment a customer pays and the moment your model runs, commercial state and application state fall out of sync. That gap is where revenue leaks and margin quietly deteriorates.

  • “Stripe says the payment succeeded. Is access actually synchronized?”

    A confirmed charge is not a valid entitlement. State drifts silently between systems.

  • “How much compute am I giving away on retries?”

    Failed and duplicated executions burn margin without producing billable outcomes.

  • “Why do two customers on the same plan produce opposite margins?”

    Usage is consumed without attribution, so profitability becomes a guess.

state · synchronization
Drift detected
Commercial state · Stripepayment.succeeded
Paid
── out of sync ──
Application state · Runtimeentitlement.missing
No access
Result: paying customers blocked, free compute granted to churned ones, and no evidence to reconcile either.
commercial ↔ application reconciliation required
02How it works

One controlled path from payment to compute.

Every AI execution passes through the same runtime pipeline. State is confirmed, access is authorized before any compute is spent, and the outcome becomes evidence you can reconcile.

  1. Commercial statepayment confirmed
  2. Entitlementssynchronized
  3. Creditsbalance available
  4. Authorizationapprove / deny
  5. ExecutionAI runs
  6. Usageconsumed safely
  7. Audit & ledgerrecorded
authorize → execute → record · retry-safe · idempotentno compute is spent before authorization
03The runtime

A single system for commercially correct execution.

Not a billing tool bolted onto your app. A coherent set of runtime modules that share one state model, one ledger and one authorization boundary.

01

Runtime authorization

Approve or deny every request before compute begins, based on live entitlement and balance state.

02

Entitlements

Translate confirmed commercial state into reliable, revocable application access.

03

Credits & balances

Prepaid and included usage tracked atomically, so limits are enforced without race conditions.

04

Usage consumption

Meter execution against the right subject, product and mode with exact attribution.

05

Retry-safe charging

Idempotent consumption ensures retries never double-charge or leak free compute.

06

Payment synchronization

Verified Stripe events reconcile commercial state into Runtime entitlements, so access follows the resulting Runtime decision.

07

Audit & ledger

Every authorization and consumption event is recorded as reconcilable, traceable evidence.

08

Reconciliation

Close the loop between commercial truth and runtime truth, continuously and provably.

04Evidence

Show it. Don’t claim it.

Reliability isn’t a marketing word — it’s a record. Every authorization, consumption and synchronization event is written to an append-only ledger you can inspect, reconcile and trust.

IdempotentAppend-onlyReconcilable
ledger · runtime events
Live
EventSubjectAmountState
  • access.checkcus_9f2c41—granted
  • usage.consumecus_9f2c411 unitrecorded
  • usage.consumecus_51ba0eretrydeduped
  • access.checkcus_77de12—denied
  • entitlement.synccus_51ba0e+2,000synced
demonstration data · illustrative only5 events · mode=live
05Future direction · ProfitLens

Economic intelligence is what we're building toward.

ProfitLens is Licenzy's future economic-intelligence direction, built on the Runtime evidence foundation. This preview shows what we're building toward, not a current production capability.

See what's nextIn developmentOperational evidence today · economic intelligence next
profitlens · roadmap preview
Coming soon
Illustrative economic signal
Roadmap
Foundation
Operational Runtime evidence from Health and events
Direction
Interpret patterns across monetized execution
Outcome
Explore future economic intelligence for operators
Status
In development — not a current production capability
Future operator guidanceExplore economic decisions built on Runtime evidence
Concept
Runtime foundation today · economic intelligence next
06Integration

Two calls stand between payment and compute.

Check access before you run the model. Consume usage after. Everything else — entitlements, credits, synchronization, audit — is handled by the runtime.

  • Authorize before compute is spent
  • Idempotent consumption, safe on retries
  • Test and live modes, cleanly separated
integration · typescript
Illustrative
// Keep the Runtime API key on your server.
const headers = {
  Authorization: "Bearer " + process.env.LICENZY_API_KEY,
  "Content-Type": "application/json",
};

// Authorize before compute — mode comes from the API key.
const accessResponse = await fetch(
  "https://api.licenzy.app/v1/access/check",
  {
    method: "POST",
    headers,
    body: JSON.stringify({ subject_ref: "customer_123" }),
  },
);
const access = await accessResponse.json();

if (!access.allowed) return deny(); // no compute spent

const result = await runModel(input);

// Consume customer entitlement usage with a stable retry key.
await fetch("https://api.licenzy.app/v1/usage/consume", {
  method: "POST",
  headers: { ...headers, "Idempotency-Key": requestId },
  body: JSON.stringify({ subject_ref: "customer_123", units: 1 }),
});
reference example · endpoints documented in /docs
200 OKgranted · credits=1204 · state=synced
Ready when compute is

Commercially correct AI execution
starts before the model runs.

Put a runtime between payment and compute. Authorize with confidence, meter safely, and keep every execution aligned with commercial state.