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

# Claim Verification

> Verify generated or user-supplied regulatory claims against published facts and citation spans.

Claim verification is a guardrail workflow. Use it when an application, assistant, or review process has drafted a legal/regulatory claim and needs to check whether the published pack supports it.

It is not the first step for most business workflows. Start with packs, obligations, applicability, evidence, and calendars; use claim verification to keep generated text grounded.

`pack_id` is required. Jurisdiction and legal domain are inferred from the
selected pack when omitted; the API never falls back to Kenya or another
jurisdiction. Claim verification remains evaluator-gated.

## Request

```bash theme={null}
curl --compressed -sS -X POST \
  "$ESHERIA_API_BASE_URL/api/v1/legal-status/verify-claim" \
  -H "content-type: application/json" \
  -H "x-api-key: $ESHERIA_API_KEY" \
  -H "idempotency-key: claim-verify-$(date +%s)" \
  -d '{
    "pack_id": "KE-CORPORATE-REGISTRY-BRS",
    "claim": "A company shall keep a register of beneficial owners.",
    "limit": 3
  }' | jq
```

## Response

Successful responses include status, publication mode, authority IDs, provision IDs, obligation IDs, citation IDs, quote spans, and any correction labels.

```json theme={null}
{
  "status": "ok",
  "data": {
    "domain_pack_id": "KE-CORPORATE-REGISTRY-BRS",
    "publication_mode": "published",
    "status": "likely_supported",
    "citation_ids": ["..."],
    "quote_spans": [
      {
        "citation_id": "...",
        "line_start": 1,
        "line_end": 1,
        "verification_status": "compiler_exact_span_candidate"
      }
    ],
    "issue_labels": ["generic_claim_profile_retrieval"]
  },
  "errors": [],
  "trace_id": "..."
}
```

## Correction Example

If a generated answer changes a deadline or statutory detail, the verifier can return `supported_with_corrections` with issue labels such as `deadline_mismatch`.

```bash theme={null}
esheria claims verify \
  --pack KE-CORPORATE-REGISTRY-BRS \
  "A company may omit its register of beneficial owners." \
  --format json
```

## When Verification Is Unsupported

Some packs may not have a promoted `claim_evaluation_profile`. In that case, claim verification returns `unsupported_capability`. The pack can still support obligation, applicability, evidence, filing-calendar, export, and graph workflows.

## Failure Modes

| Result                       | Meaning                                                | Product behavior                                         |
| ---------------------------- | ------------------------------------------------------ | -------------------------------------------------------- |
| `likely_supported`           | Published facts support the claim                      | Show the answer with citations and trace ID              |
| `supported_with_corrections` | Nearby source-backed fact supports a corrected version | Show correction context, not the original claim as final |
| `unsupported_scope`          | Claim is outside supported scope                       | Ask for a narrower claim or route to review              |
| `not_found`                  | No supporting published fact found                     | Do not present the claim as source-backed                |
| `unsupported_capability`     | Pack lacks a claim verifier                            | Use generic pack workflows instead                       |