## TL;DR

Calculated/incremental meters use usage.report; raw-events meters use events.report (reportEvent, keyed by eventName plus idempotencyKey, not featureId).

## The error

```text
usage.report returns CannotReportUsageForEntitlementWithMeterError
```

## Fix

1. Calculated/incremental meters use usage.report; raw-events meters use events.report (reportEvent, keyed by eventName plus idempotencyKey, not featureId).
   Expected: you can confirm this matches your situation.
2. Re-run the original operation and confirm the error is gone.
   Expected: no error, normal output.

## When to use

- You hit this exact error with Stigg.
- The symptom matches: usage.report returns CannotReportUsageForEntitlementWithMeterError.

## When NOT to use

- A different error message from Stigg; the cause here is specific to this error.
- Unrelated Stigg issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Stigg. Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-governance/SKILL.md.

## Variant phrasings

### usage.report returns CannotReportUsageForEntitlementWithMeterError

## Why it happens

Calling usage.report in Stigg fails with CannotReportUsageForEntitlementWithMeterError. This is a meter-type fork, not a transient error.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/stiggio/skills/blob/HEAD/skills/stigg-governance/SKILL.md