We've added more granular date filters for retrieving credit usage data.

🆕 What's new?

You can now pass specific start and end dates when retrieving credit usage data. Before this change it was only possible to pass an enum value for the desired period (e.g. last week, month, year, etc.).

⭐️ Why it matters

This update empowers you to build granular, time-based customer usage charts, providing your users with deeper insights into how they consume their credits. By isolating usage data within specific windows, you can better visualize trends, identify peak usage periods, and help customers manage their balances more effectively.

⚒️ Get started

To start building your own usage charts, head over to our API reference to see the full schema. If you use our SDKs, simply pass the startDate and endDate parameters when retrieving credit usage.

📦 Availability

The new date filters are available in the Stigg app and across our entire developer ecosystem, including GraphQL, REST, and our associated SDKs:

REST-based SDKs

• TypeScript: v0.1.0-alpha.31
• Python: v0.1.0-alpha.31
• Go: v0.1.0-alpha.29
• Java: v0.1.0-alpha.52
• Ruby: v0.1.0-alpha.29

GraphQL-based SDKs

• Node.js: v4.40.0
• Python / Java / Go / .NET: v6.10.0
• Ruby: v6.8.0

🍿 See it in action

We've added support for a value of 0 in charges and variable entitlements when provisioning and updating subscriptions. This update provides additional flexibility when managing sales-led deals and enterprise contracts via the Stigg app, API and SDKs.

🆕 What’s new?

Previously, passing a zero value for explicit subscription overrides could cause validation constraints or conflict with underlying plan defaults. With this release:

• Zero-Quantity Charges: You can now explicitly pass a quantity of 0 for line item charges.
• Zero-Value Entitlements: You can now set a value of  0  to variable entitlement.

Setting such values will disable the affected metered features.

⭐️ Why it matters

Enterprise and sales-led subscription workflows are inherently dynamic. Sales teams often negotiate custom packages that deviate from your standard pricing models.

This enhancement gives you the flexibility to:

• Enforce strict feature gating: Fully shut down access to specific variable features by overriding them to 0, rather than relying on default tiers.
• Model complex contract adjustments: Handle unique trial extensions, specific feature carve-outs, or temporary contract modifications cleanly within Stigg's provisioning logic without needing to create a separate custom plan for every single customer edge case.

⚒️ Get started

This capability is available out of the box when using Stigg's standard subscription management functions. 

🍿 See it in action

We're excited to announce Agent Skills for Claude Code - a powerful plugin that gives AI coding agents the domain knowledge they need to safely integrate Stigg into your app.

While our MCP server gives agents the tools to take action, Agent Skills give them the brains to use those tools correctly, embedding monetization best practices and strict safety guardrails directly into Claude's context window. 

⭐️ Why it matters

AI agents write great code, but they lack the structural context required for complex operations. Stigg Agent Skills solve this by providing:

• Pricing Best Practices: Teaches Claude how to structure complex pricing models, entitlement-gating, and checkout sequences cleanly.
• Subscription Sequencing: Guides Claude on handling upgrades, downgrades, and cancellations.
• Safety Guardrails: Trains the agent to avoid common monetization mistakes and protect production environments.

⚒️  Get started

Install the plugin in Claude Code or Claude Desktop today, or check out the Stigg Agent Skills Documentation for full details. 

🍿 See it in action

We're excited to announce that the Stigg CLI is now available in Public Beta.

🆕 What’s new

You can now interact with the Stigg REST API directly from your terminal using our new Command Line Interface (CLI). The Stigg CLI acts as a lightweight wrapper, allowing developers to query environments, list customers, retrieve subscriptions, and check entitlements without having to write raw HTTP requests or custom scripts.

⭐️ Why it matters

Developers need the right tools for different workflows. While our recently launched MCP Server allows you to manage Stigg using natural language, the Stigg CLI is built for speed, precision, and automation.

Understanding when to use which tool can significantly speed up your development process:

• When to use the Stigg CLI: The CLI is perfect for deterministic, programmatic workflows. It is the go-to tool for scripting automated administrative tasks, integrating Stigg commands into your CI/CD pipelines, or executing quick, repeatable queries directly from your terminal (e.g., verifying a specific customer's entitlement or listing all active plans). It requires no AI context and gives you explicit control over your environment.
• When to use the MCP Server: The MCP Server is designed for AI-driven development. It is best used within AI assistants like Cursor or Claude Desktop when you want to explore the API, scaffold code, or handle complex testing scenarios using natural language prompts without leaving your IDE.

Together, they provide comprehensive developer coverage, ensuring you can integrate and manage your pricing infrastructure securely and efficiently.

⚒️ Get started

Getting started with the CLI is as easy as 1-2-3:

1. Install the CLI via Homebrew or Go.
2. Authenticate using your environment specific API-key.
3. Use - query and manage your Stigg environments via CLI commands

For more details, check out the Stigg CLI documentation. 

We're excited to announce that the Stigg MCP Server is now available in Public Beta.

🆕 What’s new

You can now expose your Stigg environment directly to any AI agent or coding assistant that supports the Model Context Protocol (MCP) - including Claude Desktop, Cursor, ChatGPT, Windsurf, and more. Once connected, your AI assistant can interact with the entire Stigg API surface using natural language.

⭐️ Why it matters

Building and testing pricing models often requires switching between code, API documentation, and the Stigg UI. With the Stigg MCP Server, you can streamline your development and testing workflows directly from your IDE or AI chat interface without writing a single API call manually.

Your AI agent can now securely act on your behalf to:

• Manage your catalog: Create, update, and list plans, add-ons, and features.
• Handle customers & subscriptions: Provision customers, preview or create subscriptions, and grant promotional entitlements.
• Test usage & entitlements: Check if a customer has access to a specific feature, report metered usage, or submit raw metering events for testing.

⚒️ Get started

The Stigg MCP Server connects to your AI client using a standard HTTP transport or via our NPM package, authenticated securely via your Stigg environment API keys.

To connect your favorite AI assistant:

1. Generate an API key in the Stigg app under Integrations > API keys (we highly recommend creating a dedicated, scoped key for your AI client).
2. Configure your specific AI client (like Cursor, Claude, or ChatGPT) to point to the Stigg MCP Server.
3. Start asking your agent to interact with Stigg! (e.g., "Check if customer X has access to the premium feature" or "Create a new test customer and subscribe them to the Pro plan").

For step-by-step configuration snippets for all major AI clients, check out the Stigg MCP Server documentation. 

🆕 What's new

We’ve enhanced our Zuora integration to fully support termed subscriptions. You can now create subscriptions in Stigg and seamlessly sync them as termed subscriptions in Zuora, rather than relying solely on the default evergreen model.

Using specific subscription metadata keys during subscription creation, you can define the initial term length, renewal term length, period types (e.g., days, months, years), and exact renewal behaviors. Stigg automatically maps these details to the corresponding fields in Zuora.

⭐️ Why it matters

• Full Contract Control: You can precisely define if a subscription should auto-renew for another specific term, convert to an evergreen subscription upon renewal, or simply reach "Out of Term" status without auto-renewing.
• Streamlined Operations: By defining term logic directly within Stigg, you eliminate the need to manually adjust contract terms and dates in Zuora.
• Flexible Conversions: You can easily convert an existing evergreen subscription into a termed agreement (or vice-versa) straight from the Stigg UI just by updating the subscription’s metadata. Stigg will automatically issue the necessary amendment in Zuora.

⚒️ Get started

Managing termed subscriptions is handled entirely through Stigg's metadata mapping. You can learn more about termed subscription support in Stigg here.

We've decoupled the retrieval of customer usage history from their subscription lifecycle, giving you continuous and uninterrupted visibility into their activity.

🆕 What’s New

The behavior of the getUsageHistoryV2 endpoint has been extended. You can now retrieve a customer's usage history for a metered feature regardless of whether they currently have an active subscription or had one during the requested time frame.

If the customer does have an active subscription, the endpoint response includes a markers array containing the subscription's usage reset periods.

⭐️ Why It Matters

• Query usage data regardless of the subscription state
• Contextualized data: The markers array allows you to easily cross-reference raw usage data with entitlements, making it crystal clear exactly when a customer's usage was reset.

⚒️ Get Started

• GraphQL API and GraphQL-based SDKs - pass the includeInactiveSubscriptions: true parameter when calling the getUsageHistoryV2 endpoint.
• REST API and REST-based SDKs - simply call the getUsageHistory endpoint.

📦 Availability

GraphQL-based SDKs:

• Node SDK: v4.29.3
• Python / Java / Go / .NET SDKs: v6.2.3
• Ruby: v6.2.3

REST-based SDKs:

All versions

🆕 What's new

Following a successful private preview, we're excited to announce that the Stigg REST API is now available in Public Beta.

With this release, the REST API is now available to all customers and, most importantly, available for use in production environments.

⭐️ Why it matters

The transition to public beta reflects a significant step in the maturity of the REST API. Moreover, the REST API is now stable enough for use in production environments.

⚒️ Get started

To get started, call the REST API directly, or use our REST-based SDKs to get up-and-running faster in your native programming language.

We’ve decoupled the credit-granting process from the subscription lifecycle. 

🆕 What's new

You can now grant credits to customers, regardless of whether they have an active subscription. Thus, ensuring they are ready to go the moment they start using your product.

⭐️ Why it matters

This change provides the flexibility needed to handle modern SaaS onboarding and retention workflows:

• Seed New Accounts: Grant promotional or "trial" credits to leads before they even select a plan.
• Customer Support Flexibility: Quickly issue credits to customers whose subscriptions may have lapsed or haven't started yet.
• Reduced Friction: Sales and Support teams no longer need to wait for subscription creation to provide value to a user.

⚒️ Get started

To grant credits to a customer without a subscription:

1. Navigate to the Customers section in the Stigg App.
2. Select the specific customer.
3. Under the Credits section, click "+ Adjust Credits"
4. Enter the credit amount. For paid credits, specify the credit unit cost. 

The balance will update immediately, even if no plan is currently assigned.

🍿 See it in action

🔮 Coming up next

While credits can now be granted independently, credit consumption is still currently defined at the plan level and requires an active subscription. However, we are already working on decoupling the consumption flow as well, which will allow customers to draw down their credit balance even without a formal plan assignment. Stay tuned!