Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage
Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage: : gate each request with getMeteredEntitlement passing the amount the customer is about to consume as requestedUsage.
[Stigg official skills]: gate each request with getMeteredEntitlement passing the amount the customer is about to consume as requestedUsage. If hasAccess is false, throw 402. After allowing, report the usage event with an idempotency key or metering drifts. hasAccess stays true through the overage range: it is just billed, so block explicitly only if you configured a hard cap. Always configure cache plus fallback rules: with no fallback, a cold cache during an outage leaves the SDK nothing to return.
Context: Stigg gates in two steps: check, then report. Skipping the report underbills.
Matched source
Source: Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/references/gating.md Original query: "Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage" Key terms: call, gating, getmeteredentitlement, report, requestedusage, stigg, then, usage