> ## 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.

# Solutions And Use Cases

> API, CLI, and MCP workflows for legal teams, compliance builders, and agentic products.

Esheria is useful when a product needs regulatory data that can become a
workflow: pack versions, change events, obligations, applicability results,
filing rules, evidence requirements, penalty facts, legal review audit metadata,
forms, citations, relationship context, and claim verification.

Use this page to choose the right API, CLI, or MCP path for a legal, compliance, or technical workflow.

<Info>
  Esheria returns source-backed regulatory workflow data, not legal advice. Keep legal review in the loop for client-facing advice.
</Info>

## What Works Today

| Job to be done                    | API endpoint                                              | CLI                           | MCP                              |
| --------------------------------- | --------------------------------------------------------- | ----------------------------- | -------------------------------- |
| Discover published packs          | `GET /api/v1/domain-packs`                                | `esheria packs list`          | `esheria_list_packs`             |
| Inspect readiness and limits      | `GET /api/v1/domain-packs/{pack_id}`                      | `esheria packs inspect`       | `esheria_get_pack`               |
| Monitor pack versions             | `GET /api/v1/domain-packs/{pack_id}/versions`             | `esheria packs versions`      | `esheria_list_pack_versions`     |
| Compare legal changes             | `GET /api/v1/domain-packs/{pack_id}/diff`                 | `esheria packs diff`          | `esheria_get_pack_diff`          |
| Read change events                | `GET /api/v1/domain-packs/{pack_id}/change-events`        | `esheria packs change-events` | `esheria_list_change_events`     |
| Build an obligation register      | `GET /api/v1/domain-packs/{pack_id}/obligations`          | `esheria obligations list`    | `esheria_list_obligations`       |
| Match duties to an entity profile | `POST /api/v1/domain-packs/{pack_id}/applicability-check` | `esheria applicability check` | `esheria_check_applicability`    |
| Build a filing calendar           | `GET /api/v1/domain-packs/{pack_id}/filing-calendar`      | `esheria calendar list`       | `esheria_get_filing_calendar`    |
| Build an evidence register        | `GET /api/v1/domain-packs/{pack_id}/evidence-register`    | `esheria evidence list`       | `esheria_get_evidence_register`  |
| Triage penalties                  | `GET /api/v1/domain-packs/{pack_id}/penalty-facts`        | `esheria penalties list`      | `esheria_get_penalty_facts`      |
| Audit publication decisions       | `GET /api/v1/domain-packs/{pack_id}/legal-review-audit`   | `esheria legal-review audit`  | `esheria_get_legal_review_audit` |
| Verify a generated answer         | `POST /api/v1/legal-status/verify-claim`                  | `esheria claims verify`       | `esheria_verify_claim`           |
| Query relationship context        | `POST /api/v1/regulatory-graph/query`                     | `esheria graph query`         | `esheria_query_regulatory_graph` |
| Export a pack                     | `GET /api/v1/domain-packs/{pack_id}/export`               | `esheria packs export`        | `esheria_export_pack`            |

## Current Production Pack Coverage

The sanitized discovery release contains 69 pack records across 27 jurisdiction labels: 60 `verified_published` packs and 9 metadata-only `not_ready` records. Catalog version: `2026-07-15-v1+sha256:c5732893a6156d077166b60ea5016166ac5b178bb024162320d3a54e0ce745eb`. Use `GET /api/v1/domain-packs` for live discovery and inspect a pack before pinning its ID or version.

| Coverage area                     | Representative packs                                                                                              | Useful workflows                                                         |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| United Kingdom and European Union | `UK-OFSI-SANCTIONS`, `UK-DATA-USE-AND-ACCESS`, `EU-NIS2-CYBERSECURITY`, `EU-CSRD-ESRS`                            | Sanctions, privacy, cybersecurity, sustainability, and change monitoring |
| North and South America           | `US-OFAC-SANCTIONS`, `US-HIPAA-SECURITY-PRIVACY`, `CA-QC-PRIVACY-LAW-25`, `CO-HABEAS-DATA`                        | Sanctions, health privacy, regional privacy, and evidence workflows      |
| Asia-Pacific                      | `SG-MAS-TRM-OUTSOURCING`, `AU-AML-CTF-REFORMS`, `HK-STABLECOINS-ORDINANCE`, `IN-DIGITAL-PERSONAL-DATA-PROTECTION` | Financial services, AML/CTF, virtual assets, and privacy                 |
| Africa and Middle East            | `KE-EMPLOYMENT-LABOUR-WORKPLACE`, `ZA-POPIA-DATA-PROTECTION`, `BH-PDPL`, `UAE-DUBAI-VARA-VIRTUAL-ASSETS`          | Employment, privacy, and virtual-asset compliance                        |
| Global sources                    | `FATF-TRAVEL-RULE-R16`, `OECD-PILLAR-TWO-GLOBE`, `UN-SANCTIONS-IMPLEMENTATION`                                    | Financial crime, tax, and sanctions implementation                       |

<Card title="Browse all 69 current pack records" icon="library" href="/guides/pack-catalog">
  View the complete production catalog and readiness state for every pack.
</Card>

<Note>
  Generic pack workflows are available across the loaded packs. Claim
  verification remains evaluator-gated; choose a pack with an enabled evaluator
  when using `POST /api/v1/legal-status/verify-claim`.
</Note>

## Fastest Useful Flow

1. List packs.
2. Inspect the pack readiness label and limitations.
3. Check the current version and latest change events.
4. Run applicability for the user's entity profile.
5. Pull obligations, filing rules, evidence requirements, and penalties.
6. Verify any generated answer before displaying it.
7. Store citation IDs, quote spans, source basis, and `trace_id` with the downstream workflow.

```bash curl theme={null}
curl --compressed -sS -X POST \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/applicability-check" \
  -H "content-type: application/json" \
  -H "x-api-key: $ESHERIA_API_KEY" \
  -H "idempotency-key: $(python3 -c 'import uuid; print(uuid.uuid4())')" \
  -d '{
    "entity_profile": {
      "jurisdictions": ["UK"],
      "entity_types": ["data_controller"],
      "regulated_activities": ["personal_data_processing"],
      "data_categories": ["customer_personal_data"]
    },
    "profile_facts": [],
    "limit": 5
  }' | jq
```

```bash CLI theme={null}
esheria applicability check UK-DATA-PROTECTION-PRIVACY \
  --role data_controller \
  --activity personal_data_processing \
  --sector financial_services \
  --format json
```

```json MCP theme={null}
{
  "tool": "esheria_check_applicability",
  "arguments": {
    "pack_id": "UK-DATA-PROTECTION-PRIVACY",
    "entity_roles": ["data_controller"],
    "activities": ["personal_data_processing"],
    "sector_tags": ["financial_services"],
    "limit": 5
  }
}
```

Expected output includes applicable obligations, match reasons, applicability
status, confidence, citations, quote spans, readiness labels, limitations, and
`trace_id`.

## Vertical Plays

<Columns cols={2}>
  <Card title="Law firms" icon="scale">
    Use obligations, provisions through pack export, citations, and claim verification to prepare research-backed client notes and review generated legal answers before associates rely on them.
  </Card>

  <Card title="Fintech and digital lending" icon="landmark">
    Build data protection obligation registers, regulator-facing task lists, evidence checklists, and answer verification for product and compliance teams.
  </Card>

  <Card title="Corporate secretarial" icon="building-2">
    Use corporate registry packs, filing-calendar items, forms, provisions, and relationship context to build entity-maintenance checklists.
  </Card>

  <Card title="GRC and internal audit" icon="clipboard-check">
    Convert obligations into controls, evidence requirements, audit tasks, and traceable source-backed registers.
  </Card>

  <Card title="HR, payroll, and employment" icon="users">
    Use employment and payroll packs as they are published to build workplace obligations, filing dates, and evidence checklists.
  </Card>

  <Card title="Tax and finance operations" icon="calculator">
    Use tax and VAT packs as they are published to create filing calendars, recordkeeping checklists, and entity-profile workflows.
  </Card>

  <Card title="Financial crime and AML" icon="shield-alert">
    Use AML/CFT packs as they are published to map obligations to controls, evidence, customer-risk workflows, and reporting calendars.
  </Card>

  <Card title="AI and legal-tech builders" icon="bot">
    Use claim verification, citation context, and MCP tools to keep generated answers grounded in published regulatory facts.
  </Card>
</Columns>

## Example Plays

### UK Fintech Privacy Register

Business question:

> We are a UK fintech acting as a data controller and processing customer personal data. What obligations should product, legal, and compliance review first?

Call applicability, then turn returned obligations into tasks.

```bash CLI theme={null}
esheria applicability check UK-DATA-PROTECTION-PRIVACY \
  --role data_controller \
  --activity personal_data_processing \
  --sector financial_services \
  --format json
```

Then fetch the evidence register:

```bash CLI theme={null}
esheria evidence list UK-DATA-PROTECTION-PRIVACY --format json
```

Then inspect penalty facts and review audit metadata through the API:

```bash curl theme={null}
curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/penalty-facts?limit=25" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq

curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/legal-review-audit?limit=25" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq
```

### Corporate Registry Checklist

Business question:

> Which corporate registry duties, forms, and filings should a company secretary monitor?

Start with a UK Companies House pack and calendar-facing workflow:

```bash CLI theme={null}
esheria packs inspect UK-CORPORATE-REGISTRY-COMPANIES-HOUSE-ECCTA
esheria calendar list UK-CORPORATE-REGISTRY-COMPANIES-HOUSE-ECCTA --format json
esheria packs export UK-CORPORATE-REGISTRY-COMPANIES-HOUSE-ECCTA --include-all-forms --out companies-house-pack.json
```

### AI Answer Guardrail

Business question:

> Can we show this generated regulatory answer to a user?

Verify the claim before display:

```bash CLI theme={null}
esheria claims verify \
  --pack UK-DATA-PROTECTION-PRIVACY \
  "A controller must respond to a valid data subject access request within the applicable statutory period." \
  --format json
```

This claim example uses one currently evaluator-enabled pack; it is not a
jurisdiction default. If the selected pack returns `unsupported_capability`,
use its generic obligation, applicability, evidence, penalty, relationship,
and change workflows instead. For any `not_found` or
`supported_with_corrections` result, show the limitations and corrections
rather than presenting the answer as settled.
