Skip to main content

Enforcement Data

Structured enforcement actions from the FTC, HHS, and 19 state attorneys general. Each event includes the entity, fine amount, violation types, laws cited, remedies, and a link to the official source.

Why teams use enforcement data

In-house legal teams need to know when regulators take action in their industry. An enforcement event against a competitor or vendor can trigger contract reviews, policy updates, and board reporting. This data turns those events from scattered press releases into structured, searchable records that feed directly into legal workflows. Common use cases:
  • Monitor enforcement actions relevant to your industry
  • Scan vendor contracts when a new violation type emerges (using search_terms)
  • Auto-create matters in your legal workspace when high-risk events drop
  • Track enforcement trends by jurisdiction or violation type for compliance reporting

What’s included

Every enforcement event contains:

Example: searching enforcement actions

Call search_enforcement_actions with filters to find relevant events:
Abbreviated response:
See MCP: Enforcement Data for the full search_enforcement_actions tool reference, or API Reference for direct REST access.

Jurisdictions covered

21 federal and state authorities:

Violation types

18 categories organized by data subject:

Risk levels

Access methods

Enforcement data is available through:
  1. MCP Server: Use search_enforcement_actions, get_enforcement_details, and get_enforcement_stats tools. See MCP: Enforcement Data.
  2. Web Console: Browse and filter events at courtrules.app/enforcement.

Data quality

  • Every event sourced from official government press releases
  • Entity names normalized for consistent search and deduplication
  • No duplicate events across overlapping sources
  • Source quotes preserved for traceability
  • Data refreshed when government pages are updated

Data freshness

New enforcement events appear within 24 hours of the official government announcement. Source-specific timing: To get only new events since your last check, use date_from with search_enforcement_actions:
Webhook notifications for new events are on the roadmap. For now, poll with date_from filters.