Court Rules website screenshot

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 20 more developer resources.

29.7/100 thin ▲ 8.1 Agent 12/100 agent aware Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
1 API 1 MCP Servers
Legal DataCourtRulesComplianceUS Law

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0
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/.
Show this score on your site. Kin Score badge preview for Court Rules It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/courtrules/"><img src="https://apis.io/badge/courtrules/card.svg" alt="Court Rules on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
9 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Courtrules · a person reads this and replies by email.
or email info@apis.io
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 the provider profile at artifacts.apis.io/courtrules/apis.yml: open an issue on github.com/api-evangelist/courtrules to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (documented)
measured — observed by APIs.io (verified)

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

Court Rules API pricing

Rate limits

Rate-limit details →

Rate Limits 1

Documented rate limits and quota policies.

Court Rules Rate Limits

3 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Court Rules

12 quoted statements, read from Court Rules's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Court Rules

16 quoted statements, read from Court Rules's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Court Rules

3 quoted statements, read from Court Rules's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Court Rules

1 quoted statement, read from Court Rules's own page on 2026-11-09.

AI PREFS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Court Rules

2 quoted statements, read from Court Rules's own page on 2026-11-09.

LICENSE

Security Posture 2

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

Court Rules Authentication

1 scheme

SECURITY

Court Rules Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 6

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: courtrules
name: Court Rules
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
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:
- type: IntegrationEdges
  url: integrations/courtrules-integration-edges.yml
- 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
- type: UsageTerms
  url: terms/courtrules-terms-of-service.yml
- type: DataProcessing
  url: privacy/courtrules-privacy-policy.yml
- type: Eligibility
  url: eligibility/courtrules-eligibility.yml
- type: AIPreferences
  url: ai-preferences/courtrules-ai-preferences.yml
- type: DataLicense
  url: data-license/courtrules-data-license.yml
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-enrichment:
  date: '2026-10-02'
  status: enriched
  artifacts_added: 19
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Court Rules API — frequently asked questions

Does Court Rules have an API?

Yes. APIs.io lists 1 API from Court Rules, including Court Rules API.

How do I authenticate with the Court Rules API?

Court Rules uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Court Rules Authentication.

Does Court Rules have an MCP server?

Yes. APIs.io lists 1 MCP server for Court Rules: Remote MCP server at mcp.courtrules.app.

Is the Court Rules API ready for AI agents?

Court Rules has a Kin Score of 29.7 out of 100 (thin) and an Agent Readiness score of 12.1 (agent-aware), scored by API Evangelist on 2026-11-13.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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