Courtrules App Court Rules API
69
AI ReadinessAI-Aware (B+)69/100
Official vendor OpenAPI document · agent-readySecurityCompliancebearer13 EndpointsREST
For Agents
Check legal filings for compliance with federal and local court rules, classify PDF documents, and retrieve judge-specific rules, citations, and court holidays.
Use for: Check whether this motion complies with the court's filing rules, Classify this PDF before running a compliance check, Get the filing rules for a specific federal judge, List all federal district courts
Not supported: Does not handle court e-filing submission, case docket retrieval, or legal research. Use for checking filings against court rules only.
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.
Install Jentic One Beta
Connect the Court Rules API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Court Rules API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcourtrules.app%2Fcourtrules" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcourtrules.app%2Fcourtrules" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Court Rules API.
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
Patterns agents use Court Rules API for, with concrete tasks.
★ 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.
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.
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.
List the available federal courts, then retrieve the court holidays for one district
Key Endpoints
13 endpoints — the court rules api checks legal filings against federal and local court rules, returning deterministic compliance results for each document.
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
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
Jentic AI Readiness Score
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.
C
Court Rules API
- AI-Aware (B+)69/100
71
Foundational Compliance72
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience94
Agent Usability60
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
83%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
72
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
17%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
71%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
73%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
48%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Court Rules API through Jentic.
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.
GET STARTED