pack_id explicitly, then use that
same ID across API, CLI, and MCP workflows.
The sanitized discovery release contains 69 pack records across 27 jurisdiction labels. 60 are verified_published; 9 remain discoverable as not_ready metadata records without published legal-status facts. Catalog version: 2026-07-15-v1+sha256:c5732893a6156d077166b60ea5016166ac5b178bb024162320d3a54e0ce745eb.
View the complete production catalog
Browse every current pack, jurisdiction, legal domain, readiness state, and
published-fact count from the July 13, 2026 production snapshot.
Discover Packs
Omit the jurisdiction filter to discover everything entitled to the token, or filter by any jurisdiction returned by the catalog.Select A Pack Explicitly
jurisdictionlegal_domainreadiness_labellimitationspublished_legal_status_count- current version and version history
Version History And Diffs
Use the selected pack ID rather than relying on a product-wide default.Multi-Jurisdiction Examples
These are examples, not defaults. Any entitled
verified_published pack can
use the generic pack workflows for obligations, applicability, filing calendar,
evidence, penalties, legal-review-audit, versions, diffs, change events,
relationships, and export.
Claim verification is evaluator-gated. A pack may return
unsupported_capability for claim verification while its generic fact
workflows remain available.
Readiness Labels
Production API mode serves published rows only. Internal draft and
citation-verification tiers are not customer API tiers.