canonical: https://jentic.com/apis/courtrules.app/courtrules

# Courtrules App Court Rules API

The Court Rules API checks legal filings against federal and local court rules, returning deterministic compliance results for each document. It classifies uploaded PDFs, looks up the rules and citations tied to a specific judge, and lists courts, judges, and court holidays by district. Source rule documents and reference PDFs such as the FRCP are available for citation.

## For AI agents

Check legal filings for compliance with federal and local court rules, classify PDF documents, and retrieve judge-specific rules, citations, and court holidays.

## Scope

Does not handle court e-filing submission, case docket retrieval, or legal research. Use for checking filings against court rules only.

## Capabilities

- Check a legal filing against the court rules that apply to its district and judge
- Classify an uploaded PDF document to determine which compliance checks apply
- Look up the filing rules and citations tied to a specific judge
- List federal courts and retrieve details for a single district
- Retrieve court holidays for a specific district
- Search extracted filing rules across courts
- Download source rule documents and reference PDFs such as the FRCP

## Use cases

### Automated Filing Compliance Agent

An AI agent preparing a court filing can classify the document, then check it against the federal and local rules for the target district and judge and return a pass or fail result with the specific rules that were violated. This lets the agent catch formatting and procedural defects before a filing is submitted, instead of discovering them after a clerk rejects it.

Example prompt: Classify a motion PDF and run a compliance check against the selected district's rules, then list any rules the document violates

### Judge-Specific Rule Lookup

Litigation teams can retrieve the standing rules, preferences, and citations tied to an individual judge before drafting a filing. The Court Rules API returns a judge profile with its rule citations and the extracted filing rules that apply, so drafters follow the correct local practice for that courtroom.

Example prompt: Retrieve the profile and rule citations for a selected judge and summarize the formatting requirements

### Court Holiday and Deadline Reference

Case-management tools can pull the list of courts and their holidays by district to inform filing-deadline calculations. The Court Rules API lists federal courts, returns details for a single district, and provides that district's court holidays so downstream scheduling logic uses the right dates.

Example prompt: List the available federal courts, then retrieve the court holidays for one district

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/check` | Check document compliance |
| POST | `/api/v1/classify` | Classify a PDF document for compliance checking |
| GET | `/api/v1/courts` | List all courts |
| GET | `/api/v1/rules` | Get rules for a judge |
| GET | `/api/v1/judges` | List judges |
| GET | `/api/v1/extracted-rules` | Search extracted filing rules |
| GET | `/api/v1/holidays` | List court holidays |
| GET | `/api/v1/profile` | Get judge profile with citations |

## Key resources

- **Courts** — List federal courts and retrieve details and holidays for a specific district
- **Judges** — List judges and retrieve a judge profile with rule citations
- **Rules** — Get the filing rules for a judge and search extracted rules across courts
- **Documents** — List source documents and download source and reference PDFs such as the FRCP
- **Compliance** — Classify a PDF document and check it against the applicable court rules

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 71 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/courtrules.app/courtrules/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Court Rules API by hand means managing its bearer token, learning how to upload and classify PDF documents, and matching each filing to the right district and judge rules yourself. Through Jentic you install once, import the Court Rules API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Court Rules API carries the court district id in the URL path, such as `/api/v1/courts/{district_id}`, so a rule can pin your agent to specific districts. You choose which operations it may call, so it can run compliance checks and look up rules without reaching anything you did not include.
- **Credential handling:** Your Court Rules bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check a filing for compliance' or 'get the rules for a judge', and Jentic returns the matching Court Rules operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **UniCourt Enterprise APIs** — UniCourt serves court case and docket data, while the Court Rules API checks filings against court rules.
- **PACER** — PACER retrieves federal court records and dockets that pair with the Court Rules API's compliance checks.
- **Congress.gov API** — Congress.gov supplies federal legislative data that complements the Court Rules API's filing-rule reference content.

## FAQ

### What authentication does the Court Rules API use?

The Court Rules API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. The token is issued from the provider's console dashboard. When you connect the API through Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### Can I check a document for compliance with the Court Rules API?

Yes. The compliance check operation evaluates an uploaded document against the filing rules for a chosen district and judge and returns the rules it passed or failed, and a separate classify operation identifies the document type first. You can also pull the underlying rules and judge citations to see why a check failed.

### What are the rate limits for the Court Rules API?

The OpenAPI spec does not specify rate limits for the Court Rules API. Check the provider's documentation at https://courtrules.app for the current limits that apply to your API token.

### Can I limit what my agent is allowed to do with the Court Rules API?

Yes. The Court Rules API exposes read and compliance-check operations, and court-scoped lookups put the district id in the URL path. Write a rule that allows only the operations your agent needs, such as listing courts, looking up judge rules, and running a compliance check, and scope the court lookups to the districts you care about. Every call the agent makes is logged.

### How do I run a filing compliance check with the Court Rules API through Jentic?

Search Jentic for 'check a court filing for compliance' and it returns the Court Rules compliance-check operation with its input schema. Import the Court Rules API from the Jentic API Directory, store your bearer token once, and your agent can classify a document and run the check. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Court Rules API MCP server?

You don't need an MCP server to give your agent the Court Rules API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the compliance and rule-lookup operations. Nothing extra loads into the agent's context until an operation is actually used.