Look up standardized areas of law and court metadata via UniCourt's Court Standards API
domain: unicourt.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate and obtain an OAuth2 access token as with any UniCourt Enterprise API call
Call CourtStandards.get_areas_of_law(q='name:"Personal Injury"', page_number=1, sort='name', order='asc') to retrieve standardized area_of_law_id values matching a query
Use the returned area_of_law_id values to filter Court Data / PACER API case searches to a specific practice area instead of relying on inconsistent free-text case-type strings from individual courts
Sort and paginate Court Standards results with the sort/order/page_number parameters when building a practice-area picker UI
Map area_of_law_id values to your own internal practice-area taxonomy once, then cache the mapping instead of re-querying on every case search
Combine Court Standards lookups with UniCourt's case-tracking/search endpoints to build new-case alerts scoped to specific practice areas
Known gotchas
Area-of-law and other court-standard identifiers are UniCourt-proprietary IDs, not standardized across other legal data vendors — integrations also pulling from PACER, CourtListener, or state court APIs need their own crosswalk
Free-text queries against standards endpoints depend on exact phrase-matching conventions; queries that don't follow the documented query-string syntax silently return zero results
Like other UniCourt Enterprise API calls, this endpoint consumes one of the account's limited active OAuth2 tokens, so high-frequency lookups in a hot path should cache results rather than re-authenticating per call
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?