Introduction

Check court filings against judge-specific rules before you file. Monitor privacy enforcement actions across 21 jurisdictions as they happen. Two structured data feeds, available through REST API and MCP.

​

Two data domains

​

Court rules

Individual judge rules, standing orders, and filing requirements for 20+ courts and 630+ judges. Three rule layers: FRCP, Local Rules, Standing Orders. Every rule traced to its source PDF with page and section numbers. Given a document’s metadata and filing context, the API checks compliance against all three layers and returns pass/fail results citing the specific rule. Try the quickstart

​

Enforcement intelligence

Privacy enforcement actions from 21 jurisdictions: FTC, HHS, and 19 state attorneys general. Each event includes entity, fine amount, violation types, laws cited, remedies, and contract search terms. Every event links to the official government source. Search by jurisdiction, date, industry, risk level, or violation type. Available through MCP and the console. Browse the data model

​

Coverage

Access to specific courts depends on your plan. Enforcement data is available through MCP and the console.

​

Data freshness

Enforcement events are never more than one day behind the official source. If a government agency publishes an action today, you can query it tomorrow. Court rules reflect the latest standing order published on each court’s website.

​

What’s next

Pick your path based on what you’re building:

• Filing compliance for litigation software: Start with the Quickstart, then explore Integration Patterns
• Enforcement monitoring for in-house legal platforms: Start with MCP: Enforcement Data, then browse Enforcement Data
• AI agent integration: See Building with AI Agents
• Evaluating the platform? See how the same brief gets different results depending on the judge