Skip to main content
Product-credit amounts are exact decimal strings. Keep them as str; do not convert them to float when precision matters.

List credit systems

The SDK follows all active pages and returns normalized CreditSystem typed dictionaries.

Customer balances

Customer operation history

Limits must be integers from 1 to 100. Operations include exact amounts, status, reason, rate snapshot, occurrence time, and source allocations.

Entity balances

pool_policy is entity_only, entity_then_customer, customer_only, or None.

Entity operation history

Allocate credits

Deallocate credits

Transfer amounts must be positive decimal strings with at most 12 decimal places. Idempotency keys are required and limited to 255 UTF-8 bytes.

Advisory usage check

usage.check() does not reserve or mutate credits.

Atomic usage tracking

usage.track() atomically evaluates the metric conversion, selects eligible sources, deducts credits, and records the operation. Entity IDs enable per-Entity attribution and configured pool policy.

Legacy wallet adapter

nozle.check_and_deduct(customer_id, feature, credits) remains available for the legacy wallet path. New product-credit integrations should use usage.check() and usage.track(). Keep reads and mutations behind authenticated backend routes and derive customer and Entity IDs from trusted identity data.