Usage and quotas
ClaimReady uses The Wo’s shared quota and Usage controls. A successful new completed triage records oneclaim_triage unit. Retrieving a result does not
record Usage.
What counts as Usage
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 returns429 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 for temporary service and quota failures.
Idempotency
Every POST requires anIdempotency-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.