Skip to main content
The building blocks of Nozle. Each concept maps to a specific part of the platform — understand these and the rest of the docs will click.

​
Plans

A plan is a pricing tier — Starter, Growth, Scale, Enterprise, or whatever you define. Each plan bundles three things:
  • Base price — a flat recurring charge (monthly or annual)
  • Usage-based charges — metered fees tied to event codes (e.g., $0.002 per API call)
  • Feature entitlements — what the plan unlocks (analytics access, SSO, custom models)
Plans are configured in the Nozle dashboard and served to your app through the API.

Plans

​
Subscriptions

A subscription assigns a customer to a plan. When a customer checks out, Nozle creates a subscription that controls what they can access and how they are billed. Subscriptions support:
  • Upgrades — move to a higher plan mid-cycle with prorated charges
  • Downgrades — move to a lower plan, at once or at the next billing period, depending on the plan transition policy
  • Cancellation — end access immediately or at the renewal boundary under merchant-defined settlement rules

Subscriptions

Checkout

​
Events

Events are usage data points sent from your application via the SDK’s track() method. Each event contains: The event pipeline flows: SDK → Nozle API → aggregation and billing. Events drive both usage-based charges and entitlement consumption (counting toward limits).

Event Pipeline

Node SDK

Python SDK

Go SDK

​
Entitlements

Entitlements define what a customer can do based on their plan. There are two types: Feature gates — boolean access checks. Either the plan includes a feature or it does not.
Usage limits — numeric caps that reset each billing period.
Entitlements are checked from a trusted backend through the can() endpoint or the Node.js, Python, and Go SDKs. React gate components render the backend-owned result without exposing customer credentials in the browser.

Entitlements Overview

Backend-authorized updates

​
Margin

Margin intelligence is what separates Nozle from a billing system. Nozle tracks the cost of each usage unit — per LLM model, per token type, per provider — and compares it against what you charge. This gives you:
  • Per-customer margin — who is profitable, who is not
  • Per-model cost tracking — which models eat into margin
  • Margin checks in can() — an estimated margin per call and an optional margin policy that warns or denies. Nozle does not send margin alerts; see Monitor margin yourself
Margin data is computed by the Nozle API and returned alongside billing data.

Margin Overview

Cost Models

​
API Keys

Nozle uses two types of API keys to separate client-safe and server-only operations: There are no separate live and test keys. Create keys under Developers > API keys.

Node SDK (secret key)

Python SDK (secret key)

Go SDK (secret key)

React SDK (public catalog + BFF checkout)