Documentation

The Licenzy runtime, documented.

Everything you need to integrate and operate the AI Monetization Runtime — from the core model to the API. Search with ⌘K or browse by area below.

Getting started

Core concepts and trust model

Understand what Stripe owns, what Licenzy owns, where runtime truth lives, and how access becomes reliable.

Prerequisites

Have these pieces ready before you start integrating the runtime API.

API keys and authentication

Authenticate every runtime request with a Licenzy runtime API key from server-side code.

Connect Stripe to Licenzy for checkout

Store Stripe credentials and the Stripe inbound webhook signing secret in Licenzy, then configure the tenant webhook destination in Stripe so checkout can update entitlement state.

Tenant webhook setup

Configure Stripe -> Licenzy inbound delivery by registering Licenzy's tenant webhook destination in Stripe and storing the Stripe inbound webhook signing secret in Licenzy.

Runtime

Products

Products are configured in the portal and referenced in runtime checkout requests by product code.

Create checkout and grant access after payment

Use Licenzy to start Stripe checkout, then grant access only after webhook-confirmed payment updates entitlement state.

Entitlements for payment-backed access

Understand how Licenzy entitlement state connects Stripe payments to access checks, subscriptions, time passes, and usage-pack consumption.

Verify access after payment with access checks

Use Licenzy runtime access checks to verify whether a subject currently has access after payment and entitlement updates.

How to verify user access after Stripe payment (without race conditions)

Stripe payment success does not automatically mean access is active. Access should be verified against entitlement-backed runtime state after webhook-confirmed billing updates, and Licenzy provides the backend checks for that flow.

Usage & credits

Usage metering for credits and usage packs

Consume credits or usage-pack units from your backend with access checks, idempotency keys, and insufficient-usage handling.

How to sell AI credits with Stripe

Learn how to sell AI credits with Stripe, check access and safely consume usage after each generation, API call or compute action.

How to implement usage-based billing with Stripe

Stripe can collect payment for metered products, but your app still needs runtime usage tracking, entitlement-backed access, and safe consumption logic. Licenzy helps connect checkout, entitlement state, and usage consumption.

Full Licenzy and Stripe integration example

Build the full backend flow from frontend checkout to Stripe payment, webhook processing, Licenzy entitlements, access checks, and optional usage consumption.

Webhooks

Webhook and event architecture

Understand how Stripe billing signals become entitlement state, runtime access decisions, and outbound Licenzy events.

Inbound Stripe lifecycle

Understand how Stripe tenant webhook delivery enters Licenzy, what setup it depends on, and why billing signals arrive asynchronously.

Runtime state propagation

See how billing signals become entitlement transitions, access decisions, runtime reads, and customer-facing propagation.

Outbound Licenzy webhooks

Understand Licenzy's customer-facing outbound event stream and how it differs from inbound Stripe billing delivery.

Outbound webhook delivery contract

Implement production-safe Licenzy webhook receivers with the right assumptions about delivery semantics, retries, verification, and fast acknowledgements.

Refund and dispute lifecycle

Understand how refunds, disputes, and expired checkout attempts affect entitlement state and runtime access.

Operations

Manual portal operations and runtime effects

Understand how operator-driven portal actions affect runtime entitlements, access state, and outbound propagation.

Support and operational investigation

Use the Licenzy portal for customer investigation, outbound webhook delivery inspection, and manual entitlement recovery. Keep runtime endpoints focused on backend and app integration.

Delivery debugging and retry visibility

Use the Licenzy portal to inspect outbound deliveries, understand failed attempts, and monitor automatic retry state during support workflows.

Test mode vs live mode

Environment selection is key-driven. Runtime requests do not carry mode in the body.

Go live checklist

Use this checklist before sending real customers through Licenzy-powered checkout.

Reference

Licenzy API reference

Reference the Licenzy /v1 runtime API for checkout, access checks, entitlements, and usage consumption. Configure projects, API keys, Stripe setup, outbound Licenzy webhooks, and billing from the Licenzy portal.