Lex Machina
Lex Machina is a legal analytics platform owned by LexisNexis that transforms raw court documents and dockets into structured datasets so litigators, corporate legal teams, insurers, and judges can make data-driven decisions about cases, courts, judges, lawyers, parties, and damages. The platform covers all 94 federal district courts, the 13 federal courts of appeals, the PTAB, the ITC, bankruptcy courts, and a growing list of state courts (with 18M+ additional state cases for party analytics), and tracks 8,000+ judges, 6,000+ expert witnesses, 146M+ counsel mentions, and 149M+ party mentions across 10M+ cases and 45M+ documents. Lex Machina exposes its Legal Analytics through a public Litigation Analytics API (OAuth 2.0, JWT bearer tokens) at api.lexmachina.com with synchronous Python and Node.js client libraries plus an A2A (Agent-to-Agent) agent for AI/agent integrations. Practice area coverage includes Antitrust, Bankruptcy, Commercial, Consumer Protection, Contracts, Copyright, Employment, ERISA, Insurance, Patent, Product Liability, Securities, Tax, Torts, and Trademark litigation. Lex Machina was founded in 2010 as a Stanford University Law School spin-out and was acquired by LexisNexis (RELX) in 2015.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Lex Machina the way a machine reads it — 71 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lex Machina scores 32.9/100 (thin), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Lex Machina's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lex-machina/"
title="Lex Machina on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lex-machina.svg"
alt="Lex Machina Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/lex-machina/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lex-machina/"
title="Lex Machina on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lex-machina/card.svg"
alt="Lex Machina Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Lex Machina
Each block below is one kind of artifact we hold for Lex Machina. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lex Machina Alerts API
Alerts.
Lex Machina Attorneys API
Attorney data.
Lex Machina Authorization API
Provides API authorization.
Lex Machina Bankruptcy Cases API
Bankruptcy court cases.
Lex Machina Case Query API
Provides a filter based way to find cases.
Lex Machina Dockets API
Docket data.
Lex Machina Entities API
Entity data.
Lex Machina Federal Appeals Cases API
Federal court of appeals cases.
Lex Machina Federal District Cases API
Federal district court cases.
Lex Machina ITC Investigations API
ITC Investigations.
Lex Machina Judges API
Judge data.
Lex Machina Law Firms API
Law firm data.
Lex Machina List API
Provides cannonical lists for specific fields.
Lex Machina Parties API
Party data.
Lex Machina Patents API
US patent data.
Lex Machina PTAB Trials API
PTAB Trials.
Lex Machina State Cases API
State court cases.
Lex Machina Status API
Provides API status.
Scroll within the panel for all 18 ·
Open Collections 23
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLex Machina Alerts API
OPEN COLLECTIONLex Machina Alerts Analytics API
OPEN COLLECTIONLex Machina Alerts Attorneys API
OPEN COLLECTIONLex Machina Alerts Authorization API
OPEN COLLECTIONLex Machina Alerts Bankruptcy Cases API
OPEN COLLECTIONLex Machina Alerts Case Query API
OPEN COLLECTIONLex Machina Alerts Dockets API
OPEN COLLECTIONLex Machina Alerts Entities API
OPEN COLLECTIONLex Machina Alerts Federal Appeals Cases API
OPEN COLLECTIONLex Machina Alerts Federal District Cases API
OPEN COLLECTIONLex Machina Alerts Find API
OPEN COLLECTIONLex Machina Alerts ITC Investigations API
OPEN COLLECTIONLex Machina Alerts Judges API
OPEN COLLECTIONLex Machina Alerts Law Firms API
OPEN COLLECTIONLex Machina Alerts List API
OPEN COLLECTIONLex Machina Alerts Parties API
OPEN COLLECTIONLex Machina Alerts Patents API
OPEN COLLECTIONLex Machina Alerts PTAB Trials API
OPEN COLLECTIONLex Machina Alerts Search API
OPEN COLLECTIONLex Machina Alerts State Cases API
OPEN COLLECTIONLex Machina Alerts Status API
OPEN COLLECTIONLex Machina API
OPEN COLLECTIONScroll within the panel for all 23 ·
Features 25
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 25 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lex Machina — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lex-machina · machine-readable index on apis.io
This is an independent, third-party profile of Lex Machina, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.