Court Rules

Court Rules provides structured legal and enforcement data from U.S. federal and state courts, including judge rules, filing deadlines, court holidays, and enforcement actions. The platform offers an API that enables developers to integrate court rule searches, compliance checks, and legal intelligence into products, supporting both free tier access and paid plans for higher volume and advanced features.

Court Rules is listed with 1 API on the APIs.io network. Tagged areas include Legal Data, CourtRules, Compliance, and US Law.

Court Rules’ developer surface includes authentication, getting-started guide, API reference, documentation, signup flow, support, engineering blog, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

29.2/100 thin ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

1 API 1 MCP Servers

Legal Data CourtRules ComplianceUS Law

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 29.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 8.1 / 17

Access Clarity 5.8 / 17

Operational Transparency 3.5 / 11

Contract Governance 0.5 / 10

Discoverability 5.8 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/courtrules: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Court Rules API

Deterministic court rules compliance checking for federal filings

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Court Rules MCP Server

Remote MCP server at mcp.courtrules.app.

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Courtrules Rate Limits

3 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Courtrules Authentication

1 scheme

SECURITY

Courtrules Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 4

Properties that don't map to a standard resource type

AgentCard

Hosts

Vendors

Leadership

Source (apis.yml)

aid: courtrules
name: Court Rules
image: https://www.courtrules.app/opengraph-image?a428ae78c988eff6
description: Court Rules provides structured legal and enforcement data from U.S. federal and state courts, including judge
  rules, filing deadlines, court holidays, and enforcement actions. The platform offers an API that enables developers to
  integrate court rule searches, compliance checks, and legal intelligence into products, supporting both free tier access
  and paid plans for higher volume and advanced features.
url: https://raw.githubusercontent.com/api-evangelist/courtrules/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-02 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-02'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
tags:
- Legal Data
- CourtRules
- Compliance
- US Law
tags_raw:
- LegalData
- API
- CourtRules
- Compliance
- USLaw
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.courtrules.app/blog/feed
  type: BlogRSS
- type: RateLimits
  url: rate-limits/courtrules-rate-limits.yml
- type: Authentication
  url: authentication/courtrules-authentication.yml
- type: Conformance
  url: conformance/courtrules-conformance.yml
- type: LLMsTxt
  url: llms/courtrules-llms.txt
- type: AgentCard
  url: a2a/courtrules-a2a.yml
- type: MCPServer
  url: mcp/courtrules-mcp.yml
- type: WellKnown
  url: well-known/courtrules-well-known.yml
- type: Hosts
  url: hosts/courtrules-hosts.yml
- type: Vendors
  url: vendors/courtrules-vendors.yml
- type: Leadership
  url: https://www.courtrules.app/team
- type: GettingStarted
  url: https://docs.courtrules.app/quickstart
- type: APIReference
  url: https://docs.courtrules.app/api-reference/overview
- type: DomainSecurity
  url: security/courtrules-domain-security.yml
- type: Website
  url: https://www.courtrules.app/
- type: Documentation
  url: https://www.courtrules.app/api
- type: SignUp
  url: https://www.courtrules.app/api
- type: TermsOfService
  url: https://www.courtrules.app/terms
- type: PrivacyPolicy
  url: https://www.courtrules.app/privacy
- type: Support
  url: https://www.courtrules.app/support
- type: Blog
  url: https://www.courtrules.app/blog
apis:
- name: Court Rules API
  description: Deterministic court rules compliance checking for federal filings
  humanURL: https://docs.courtrules.app/api-reference/overview
  baseURL: https://api.courtrules.app
  aid: courtrules:court-rules-api
x-submission-notes: U.S. court rules, judge procedures and privacy-enforcement data API with filing-compliance checks. Submitted
  3x (notices 2880, 2881, 2883).
x-submission-probe: root 200; /api 200 (endpoints, pricing, free tier); llms.txt 200; MCP mcp.courtrules.app/mcp 401 (Bearer);
  no OpenAPI; 404 probe 404
x-submitted-by: courtrules.team@gmail.com (apis.io/add, 2026-09-30)
x-enrichment:
  date: '2026-10-02'
  status: enriched
  artifacts_added: 19
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/courtrules"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/courtrules/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/courtrules/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.