Skip to main content
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.
Esheria returns source-backed regulatory workflow data, not legal advice. Keep legal review in the loop for client-facing advice.

What Works Today

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.

Browse all 69 current pack records

View the complete production catalog and readiness state for every pack.
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.

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.
curl
CLI
MCP
Expected output includes applicable obligations, match reasons, applicability status, confidence, citations, quote spans, readiness labels, limitations, and trace_id.

Vertical Plays

Law firms

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.

Fintech and digital lending

Build data protection obligation registers, regulator-facing task lists, evidence checklists, and answer verification for product and compliance teams.

Corporate secretarial

Use corporate registry packs, filing-calendar items, forms, provisions, and relationship context to build entity-maintenance checklists.

GRC and internal audit

Convert obligations into controls, evidence requirements, audit tasks, and traceable source-backed registers.

HR, payroll, and employment

Use employment and payroll packs as they are published to build workplace obligations, filing dates, and evidence checklists.

Tax and finance operations

Use tax and VAT packs as they are published to create filing calendars, recordkeeping checklists, and entity-profile workflows.

Financial crime and AML

Use AML/CFT packs as they are published to map obligations to controls, evidence, customer-risk workflows, and reporting calendars.

AI and legal-tech builders

Use claim verification, citation context, and MCP tools to keep generated answers grounded in published regulatory facts.

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.
CLI
Then fetch the evidence register:
CLI
Then inspect penalty facts and review audit metadata through the API:
curl

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:
CLI

AI Answer Guardrail

Business question:
Can we show this generated regulatory answer to a user?
Verify the claim before display:
CLI
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.