You can now consume credits directly in Stigg without requiring an active subscription. This allows you to use Stigg as a standalone credits engine for tracking balances, enforcing entitlements, and governing usage, while managing subscriptions entirely in your own platform.

✨ What's New

Previously, consuming credits through reportUsage or reportEvent required customers to have an active subscription with credit-based entitlements. With this release, credits can now be consumed directly against customer credit grants, completely bypassing the subscription layer.

This enables two common use cases:

• Standalone credits engine: Use Stigg as a dedicated credits engine while managing subscriptions in your own billing system.
• Hybrid integration: Integrate an existing credit model with Stigg to track balances, consume credits, and enforce entitlements.

The release includes:

• Direct UI & API consumption: Grant promotional or paid credits using the existing grantCredit functionality and consume directly against those grants.
• Full ledger visibility: Complete visibility in the credit ledger for every credit grant and consumption event.
• New SDK capabilities: Call getCreditEntitlement, consumeCredits, and consumeCreditsAsync for customers without any active subscription.

⭐️ Why It Matters

Not every product needs subscription management. Many teams already have an existing billing platform or custom subscription system and simply need a reliable way to manage credits and enforce usage.

Direct credit consumption enables you to:

• Decouple credits from subscriptions: Build usage-based products without coupling credits to subscription lifecycles.
• Keep your billing platform: Retain your existing subscription or billing platform while offloading the consumption logic.
• Audit every single action: Track every credit grant and consumption event reliably in the Stigg ledger.

📦 Availability

Direct credit consumption is available in the Stigg app and across our developer ecosystem, including GraphQL, REST, and our associated SDKs:

REST-based SDKs

• TypeScript: v0.1.0-beta.36
• Python: v0.1.0-beta.31
• Go: v0.1.0-beta.33
• Java: v0.1.0-beta.31
• Ruby: v0.1.0-beta.35

GraphQL-based SDKs

• Node.js: v4.48.0
• Python / Go / .NET: v6.16.0
• Java: v6.17.0
• Ruby: v6.14.0