> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thewo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage and quotas

> ClaimReady Usage units, quota behavior, and idempotent retries.

# Usage and quotas

ClaimReady uses The Wo's shared quota and Usage controls. A successful new
completed triage records one `claim_triage` unit. Retrieving a result does not
record Usage.

## What counts as Usage

| Request outcome | `claim_triage` Usage |
| - | -: |
| New successful completed POST | 1 unit |
| Replay of a completed request with the same key and material input | No additional unit |
| Known unsupported `claimDomain` | No successful completed Usage unit |
| GET of a customer-owned result | 0 units |

A recognized unsupported domain is rejected with `422 unsupported_claim_scenario`.
A structurally valid supported request can complete with missing optional
purchase, policy, or evidence facts; those gaps appear in the result.

## Quota and rate limits

Quota applies to successful new triage operations. When the operation quota is
exhausted, POST returns `429 quota_exceeded` with safe operation and quota
status details. The applicable plan and limits are shown through current
product access surfaces when available; these docs do not publish private plan
economics.

Technical rate limits are separate from Usage quota. A rate-limited request
returns `429 rate_limit_exceeded`; follow `Retry-After` when supplied. See
[Errors](https://docs.thewo.io/claim-ready/guides/errors.md) for temporary service and quota failures.

## Idempotency

Every POST requires an `Idempotency-Key` up to 255 characters. Use the same key
when retrying the same logical request. A completed identical request replays
its original response without a second triage or Usage unit. If the same key is
used with materially different input, including a different `claimDomain`, the
API returns `409 idempotency_conflict`. A request already being processed can
return `409 idempotency_in_progress`.

Correct malformed input before retrying. For temporary failures, use bounded
backoff and retain the same key for the same logical request. Error messages
may clarify when Usage was recorded despite a quota confirmation failure.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.