You can now reserve credits before an AI operation starts and settle the actual cost once it completes.

With Reserve & Settle, Stigg secures an estimated credit amount upfront, prevents concurrent requests from reserving the same balance, and automatically releases unused credits. It's designed for AI workloads where the final cost isn't known in advance, such as LLM completions, agent runs, and long-running jobs.

🆕 What's new?

• Reserve credits upfront - Secure an estimated amount before an operation starts, ensuring those credits are available even when multiple requests run concurrently.
• Settle the actual cost - Consume the credits used when the operation completes, automatically releasing any unused reserved amount.
• Automatically release expired reservations - Set an expiration time so abandoned or failed operations don't leave credits locked indefinitely.
• Safely retry requests - Use reservation IDs to prevent duplicate reservations or settlements.
• Track reserved balances - See reserved credits separately from consumed credits, with a clear record of reservation and settlement activity.

💡 Why it matters

AI workloads don't always have predictable costs. An LLM response might use fewer tokens than expected, an agent might execute multiple steps, or several requests might compete for the same credit balance.

Reserve & Settle lets you secure credits before work begins and charge for actual consumption afterward - without building custom reservation, refund, or reconciliation logic.

⚒️ Get started

1. Reserve credits - Call the reservation endpoint through Stigg's REST API or SDK before starting your AI operation.
2. Execute your operation - Run your LLM request, agent workflow, or background job while the reserved credits remain unavailable to other requests.
3. Settle the actual usage - Use the reservation ID to settle the final credit amount. Any unused reserved credits are automatically released.

Reservations also support expiration timeouts, ensuring abandoned operations don't leave credits locked indefinitely.

📦 Availability

Reserve & Settle is available through Stigg's REST API and REST SDKs.

REST-based SDKs

• TypeScript: v0.1.0-beta.62
• Python: v0.1.0-beta.53
• Go: v0.1.0-beta.54
• Java: v0.1.0-beta.54
• Ruby: v0.1.0-beta.59
• C#: v0.11.0

🍿 See it in action

We are excited to announce the release of the Stigg Agent Governance SDK, an open-source solution built on top of Stigg's highly scalable infrastructure, that empowers you to seamlessly meter, enforce, and govern every LLM call your product and its agents make!

🆕 What’s new?

Managing autonomous AI agents requires granular control over limits, costs, and access. The new Agent Governance SDK solves this by wrapping the LLM or gateway client you already use. By simply calling stigg.wrap(client) once, every subsequent model call goes through three critical steps:

1. Meter usage: Token counts (and costs, where supported) are automatically read from each response and reported to Stigg straight from the provider, making usage metering completely hands-off. The SDK includes native support for 18 LLM providers and gateways, including: OpenRouter, LiteLLM, Cloudflare, Databricks, Amazon Bedrock, OpenAI, Anthropic, Google Gemini, Groq, Mistral, Deepseek, Perplexity, Ollama, TypeSafe (Jev) and more. Supporting additional vendors is as easy as initializing the SDK with a recipe that defines the mapping logic.
2. Enforce access: Before a call even leaves your environment, the SDK checks that the agent has enough credits or metered capacity to perform its task. Agents that have hit their limit are blocked before they reach the provider, preventing unexpected costs.
3. Govern usage: Give each agent its own identity and budget under your teams and organizations. You’ll know exactly which agent spent what, and you can stop a single runaway agent without disrupting the rest of your system.

💡 Why it matters

• Native support for common LLM providers and gateways: Building custom metering logic takes time away from your core product. Our LLM and LLM gateway wrapping capabilities intercept calls natively, extracting usage and cost metrics automatically so you don't have to. 
• Enterprise-grade scale: The SDK is powered by Stigg's enterprise-grade infrastructure. Enjoy peace of mind with high-throughput metering capable of ingesting up to 1M+ events per second, and low-latency access enforcement that returns decisions in under 10ms.
• The power of Open Source: We've made the Agent SDK fully open source. This gives your engineering team complete transparency into how your LLM requests are handled in the request path, the flexibility to inspect and contribute to the code, and the freedom to easily customize the SDK for proprietary endpoints or internal architectures.

⚒️ Get started

1. Install the Agent SDK: npm install @stigg/agent-sdk-js
2. Read the Agent SDK documentation
3. Explore the open source library

📦 Availability

The Agent Governance SDK is available in public beta for all customers.

🍿 See it in action

Watch how simple it is to add metering, access enforcement, and governance to your AI agents:

We are excited to announce that you can now easily view the specific credit card brand (e.g., Visa, Mastercard) and digital wallet (e.g., Apple Pay, Google Pay) used as the default payment method for subscription and top-up billing in Stigg!

🆕 What’s new?

Previously, managing default payment methods didn't surface the granular details of the payment provider. With this update, Stigg now surfaces the card brand and wallet type directly within the Stigg app and via the API.

In the Stigg App, this information is now presented on the Customer Details screen, as well as during the subscription creation and top-up flows.

When using the API, the new data is available in the response of a payment method attachment and when fetching customer details using the paymentMethodDetails.brand and paymentMethodDetails.wallet properties.

💡 Why it matters

• Better Customer Support: Having immediate visibility into whether a customer is using a Visa, Mastercard, Apple Pay, or Google Pay helps streamline troubleshooting for payment or billing issues.
• Improved Customer Experience: Use new fields to provide customers with visibility on what card brand and wallet type the use to pay for their subscription.
• Unified Visibility: Your team no longer needs to cross-reference payment gateways to see how a customer is paying for their subscriptions or top-ups. Everything is seamlessly accessible right within Stigg.

⚒️ Get started

No complex setup is required. The newly added fields will appear automatically in the Stigg app and API responses.

Note: The new fields are only populated for new payment method attachments.

📦 Availability

The payment method brand and wallet properties are supported across the Stigg API and our latest SDKs:

GraphQL API clients

• Node: v5.4.0
• Python: v6.25.0
• Ruby: v6.23.0
• Java: v6.27.0
• .NET: v6.25.0
• Go: v7.2.0

REST API clients 

• TypeScript: v0.1.0-beta.58
• Python: v0.1.0-beta.50
• Ruby: v0.1.0-beta.55
• Go: v0.1.0-beta.51
• Java: v0.1.0-beta.50
• .NET: v0.10.0

Frontend SDKs

• JavaScript: v5.4.0
• React: v11.5.0

🍿 See it in action

You can now break down credit usage by feature and multiple custom dimensions at the same time, giving you a more detailed view of how credits are consumed across your customers.

Whether you're tracking usage by feature, user, site, or workspace, Stigg makes it easier to understand where credits are being spent.

🆕 What's new?

• Group usage by feature and custom dimensions: Break down credit consumption by featureId alongside up to three custom dimensions, such as userId or siteId, to see which features drive the most credit usage for each user or site.
• Explore usage in the UI: Use the new multi-select Group by filter in the customer Credits tab to analyze usage across multiple dimensions.
• Analyze historical usage: Group existing usage data by feature without changing how events are reported or adding featureId as a custom dimension.
• Query usage through the API: Retrieve multidimensional credit usage breakdowns using the REST or GraphQL API.

💡 Why it matters

Understanding total credit consumption isn't always enough. You also need to know which features are driving usage and how that consumption is distributed across users, sites, or other entities.

With multidimensional grouping, you can identify usage patterns, investigate unexpected consumption, and provide customers with more transparent credit usage reporting, without building custom analytics.

⚒️ Get started

1. Open a customer's Credits tab in the Stigg app.
2. Use the Group by filter to select Feature and up to three custom dimensions.
3. Explore the resulting usage breakdown to understand where credits are being consumed.

You can also retrieve the same breakdown programmatically using getCreditUsage with the groupBy parameter, for example: groupBy: ["featureId", "userId"]

📦 Availability

Multidimensional credit usage grouping is available now in the Stigg app and through the REST and GraphQL APIs.

We're excited to announce our native integration with Airwallex! With this integration, you can now use Airwallex to bill customers without building custom integrations.

🆕 What’s new?

• Automated Invoicing: Stigg generates invoices for subscriptions, top-ups, and usage, then pushes them to Airwallex for collection.
• Secure Payment Storage: Customer payment methods are stored directly in Airwallex. Stigg only references these methods to automatically charge for renewals and upgrades without requiring customers to re-enter their details.
• Flexible Checkout: You can use the Stigg Checkout widget to handle payments without writing payment-specific code, or build a custom checkout using Airwallex’s embedded payment form.
• Cross-Platform Links: Clicking a "billing ID" in the Stigg app directly opens the corresponding customer or invoice in Airwallex.

💡 Why it matters

• Fast Setup: Connect the integration in seconds through the Stigg UI, removing the need for custom code or ongoing engineering maintenance.
• Global Collection & Localized Payouts: AI companies rarely operate in just one market. By connecting Airwallex to Stigg, you can instantly open local accounts in over 70 countries to handle multi-currency payments seamlessly. Maintain your pricing logic in Stigg while accepting payments in local currencies, and keep those funds in their respective local accounts. This allows you to pay suppliers, contractors, and computing costs (like GPU inference) in whatever country they operate in, all without opening new bank accounts, dealing with complex FX reconciliation, or setting up a new payment integration for each market.
• Enjoy the Best of Both Worlds: Benefit from Stigg's high-throughput usage metering, real-time entitlement access control, governance and credit management, and Airwallex's financial infrastructure, managing global payment collection, invoicing, multi-currency processing, and financial reporting.

⚒️ Get started

1. Get your API credentials, Org ID, and Account ID from the Airwallex Developer dashboard.
2. In the Stigg app, go to Integrations and click Add integration.
3. Select Airwallex from the list of available integrations.
4. Enter your credentials and click Connect.

For more details, read the Airwallex integration documentation.

📦 Availability

The Airwallex integration is now available in public beta for all customers.

Getting up and running with Stigg just got significantly faster! We're excited to announce that Stigg is now available as a provider on the Stripe Projects network - allowing you and your AI agents to spin up a Stigg environment and connect it with your Stripe setup directly from your terminal with a single command.

🆕 What’s new?

• Instant Setup - With a single command using the Stripe CLI (stripe projects add stigg/environment), you can automatically create a Stigg environment directly from your terminal.
• Out-of-the-Box Integration - Your new Stigg development environment automatically connects to your Stripe account from the start, bridging your entitlement management with your billing engine.
• Instant Local Credentials - No manual copy-pasting required. Stripe Projects fetches and injects your new Stigg API keys straight into your local .env file securely.
• AI-Agent Ready - Because provisioning is deterministic and requires no manual browser setup, AI coding agents can configure and set up Stigg on your behalf while keeping you in flow.
• Real Ownership & Control - Resources live directly in your own Stigg account, maintaining normal dashboard visibility, full controls, and access whenever you need them.

💡 Why it matters

• Unprecedented Speed: Go from zero to a fully configured Stigg environment in seconds without context-switching away from your terminal.
• Unified Workflow: Get the best of both worlds - use Stigg for advanced usage metering, entitlement enforcement, and governance, while leveraging Stripe to seamlessly handle billing operations.
• Streamlined Developer Experience: Keep your focus in your code and let the CLI handle secret delivery and environment setup.

⚒️ Get started

1. Install the Stripe CLI and Projects plugin.
2. Open your terminal in your local project directory.
3. Run stripe projects add stigg/environment.

That's it - your Stigg development environment will be created and connected, with API keys injected directly into your local .env file!

For detailed setup instructions, check out our Stripe Projects Documentation.

🍿 See it in action

Managing your product catalog just got faster. We’ve optimized how the Stigg app loads Plans and Add-ons, significantly reducing load times—especially for large catalogs.

✨ What’s New

Plans and Add-ons pages now request only the data needed to render their tables, instead of fetching the full underlying catalog data.

In production environments with large catalogs, this resulted in significant improvements:

• Plans load up to 5.7× faster
• Add-ons load up to 5.5× faster
• Response payloads are significantly smaller, reducing unnecessary data transfer.

⭐️ Why It Matters

As your catalog grows, navigating and managing Plans and Add-ons shouldn’t get slower with it.

These improvements make catalog management feel faster and more responsive, with less waiting when reviewing or updating your pricing and packaging.

📦 Availability

These performance improvements are live now for all Stigg customers.

We’re introducing a new webhook event: data_export.sync_failed, designed to help you proactively monitor the health of your data exports in real-time.

🆕 What’s new?

We've added a new data_export.sync_failed webhook event, that triggers automatically whenever a scheduled or manual data export sync to your configured destination fails. 

Instead of waiting for a manual check in , your system will instantly receive an event payload containing context about the failed run, helping your team identify the issue immediately.

💡 Why it matters

• Proactive Monitoring: You no longer need to check the Stigg app manually or wait to discover stale data in your warehouse.
• Automated Alerting: Seamlessly pipe this webhook into your incident management tools (like PagerDuty or Opsgenie) or team communication channels (like a dedicated Slack channel) to alert your data or engineering team the second an issue occurs.
• Uninterrupted Data Reliability: Ensuring your Stigg data (Customer Data, Product Catalog, and Usage Tracking) successfully reaches your infrastructure is critical. This event closes the loop on data observability so you can keep your downstream reporting accurate and up to date.

⚒️ Get started

1. In the Stigg app, navigate to the Settings > Webhooks section.
2. Click + Add webhook (or edit an existing one).
3. Under the event triggers list, select the data_export.sync_failed event.

For complete details on the event payload and schema, check out the Webhook API Reference documentation.

📦 Availability

Available immediately to all customers that use the new data export pipeline.

Stigg has long provided ultra-low latency entitlement checks and fail-safe resilience when using our GraphQL-based SDKs. Today, we’re bringing those exact same high-availability features to developers integrating via REST!

With this release, customers leveraging REST-based SDKs can now benefit from < 10ms latency when performing entitlement checks by proxying requests through the Stigg Sidecar service.

🆕 What’s new?

REST-based SDKs can now benefit from the following:

• Sidecar Support: Install and deploy the Stigg Sidecar to proxy requests directly from REST-based SDKs.
• In-Memory & Persistent Caching: Configure the Sidecar service with a Redis instance to persistently cache entitlement and usage data locally across multiple nodes, or utilize out-of-the-box in-memory caching.
• Global Fallback Strategy: Configure the Sidecar service with a global fallback strategy for entitlement evaluations, ensuring default access rules apply even when data isn't cached.
• Offline Mode: Configure the Sidecar service to work in offline mode for local development and testing, allowing you to bypass Stigg API network requests entirely.

💡 Why it matters

• Sub-10ms Latency: REST API users can now resolve entitlement evaluations instantly from a local memory or Redis cache, reducing check latencies to under 10ms.
• Fail-Safe Resilience: Gain full offline resilience for your REST integrations. The Sidecar is engineered to keep serving entitlements even when the Stigg API is unreachable or network errors occur - serving cached entitlements, or fallback values for uncached ones.
• Streamlined Testing: With offline mode enabled, the Sidecar skips API key validation and limits entitlement evaluations strictly to your defined fallback values, turning other service methods into no-ops. This makes isolated testing and local development fast and predictable.

⚒️ Get started

1. Deploy the Stigg Sidecar as a shared service or alongside your main host application.
2. Provide your Sidecar deployment with connection details for your Redis instance to enable persistent caching, and/or configure default access rules using the ENTITLEMENTS_FALLBACK environment variable.
3. Update the configuration of the Stigg REST SDK to route requests through the local Sidecar proxy.

For detailed architecture diagrams and deployment instructions, check out our Stigg Sidecar Documentation.

📦 Availability

• REST is supported in the Sidecar service from v8.1.1 or later.
• Persistent caching is available for customers on the Stigg Scale plan.

We;ve moved the credit configuration out of the Plan price wizard and into a brand-new, dedicated section directly within the Plan details screen.

This architectural update was implemented to make it seamless to update and roll out credit changes to your entire customer base at scale, operating exactly like our existing entitlement rollouts.

🆕 What’s new?

• Dedicated Credit Configuration Section: The setup for feature-to-credit mapping and default top-up pricing has been decoupled from the Plan price wizard. It now lives in its own prominent, standalone section on the Plan details screen.
• Mass Subscription Rollouts: You can now roll out changes to a plan's credit configuration across millions of active subscriptions simultaneously. Whether you are adjusting how many credits a feature costs or modifying the default top-up price, propagating these updates to your users is now effortless. Any updates you roll out will only affect credit grants and deductions that take place after the change is successfully published.

💡 Why it matters

• Effortless Scalability: Managing and iterating on credit-based pricing models for a massive user base is now significantly easier. Update your credit mappings once and push them to all your subscriptions without breaking a sweat.
• Improved Visibility & Organization: Giving credit configuration its own dedicated space keeps your workspace organized, making it much faster to view, understand, and adjust how credits are consumed within your plans.

ℹ️ Important note on rollouts

Please note that changes to a feature’s price in credits and default top-up pricing are not retroactive. 

⚒️ Where to find it

1. In the Stigg app, navigate to your Plans and select any existing plan.
2. Instead of opening the Price Wizard, look directly at the Plan details screen.
3. Scroll down to locate the new, dedicated Credit configuration section to view, edit, and roll out your feature-to-credit mapping and top-up pricing!

🍿 See it in action