When a request fails, gets retried, or produces an error, you can submit a track event with a negative quantity to reverse the recorded usage. This works across all metered features, not just credits.

For credit burndown features specifically, reversed usage returns credits to the customer's balance via an adjustment grant. Adjustment grants accumulate across multiple corrections per company, are always consumed before plan grants or purchased credits, and carry a rolling one-year expiration that extends with each new adjustment.

Negative quantity events require a server-side secret API key (publishable keys cannot submit them) and generate negative usage records in the ledger for auditing. See the usage adjustments docs for implementation details and code examples.

Switch between light, dark, and system themes from the account menu. The sidebar has three modes: collapsed (icon-only), standard, and expanded.

Both preferences persist across sessions. No configuration required.

Every price type in Schematic now supports multiple currencies: plan and add-on base prices, overage pricing, pay-as-you-go, pay-in-advance, tiered pricing, credit costs, and credit bundle pricing.

Customers select their preferred currency during checkout, and the correct price carries through the pricing table and checkout flow. Currency configuration is managed in the catalog alongside your existing plan setup.

Ruby teams can integrate Schematic with a native SDK that covers the full API surface: flag checks, identify and track calls, company and plan management, and entitlement lookups. The SDK includes local caching for flag checks with configurable TTL and max size, an event buffer that batches track and identify calls to reduce network overhead, and an offline mode for testing.

Install via gem install schematic and see the GitHub repo and SDK docs for setup.

Install Schematic from the Stripe App Marketplace to view and manage entitlements, usage, and plan state without leaving Stripe. The app surfaces each customer's current plan, feature access, usage against limits, and any active overrides or trials right alongside their Stripe subscription and payment data.

Your billing and RevOps teams can apply overrides, adjust entitlements, and see expansion signals without switching contexts.

Install from the Stripe App Marketplace and read the Stripe integration docs to connect your account.

Hard limit UX — Optionally surface hard limits in components alongside monetized entitlements with soft limits like overages, pay in advance, etc. Hard limits are themselves optional, displaying them is now any option too.

Improved invoice display — The invoice view in the customer portal has been updated for clarity. Formatting and display logic improvements make billing history easier to read.

Usage bar fix for overage entitlements — The usage bar was rendering incorrectly for entitlements in overage. This is now fixed and accurately reflects over-limit usage state.

checkFlagWithEntitlement is now available across more SDKs. This method returns not just the flag value (true/false) but the full entitlement context: usage, allocation, credit balance, and the reason for evaluation. This is the right call to make when you need to render feature states like usage meters, upgrade prompts, hard limit walls.

• Node.js — checkFlagWithEntitlement + datastream support + Replicator support

• Go — checkFlagWithEntitlement now available

• C# — checkFlagWithEntitlement now available

The datastream and Replicator additions to the Node SDK mean enterprise customers using Schematic's pre-computed entitlement delivery can now use the Node SDK with the same low-latency, cached evaluation path available in other SDKs.

Docs:

Node Effective Entitlements: https://docs.schematichq.com/developer_resources/sdks/nodejs#checking-flags-with-entitlement-details

Node Datastream: https://docs.schematichq.com/developer_resources/sdks/nodejs#datastream

Go Entitlements: https://docs.schematichq.com/developer_resources/sdks/go#checking-flags-with-entitlement-details

C# Entitlements: https://docs.schematichq.com/developer_resources/sdks/csharp#checking-flags-with-entitlement-details

You can now issue read-only API keys from the Schematic dashboard. Read-only keys are restricted to GET operations. They cannot create, update, or delete any resources. Flag check routes (which use POST under the hood) are correctly permitted on read-only keys.

This is useful for giving read access to agents, internal tooling, analytics pipelines, or third-party integrations without exposing write permissions.