Search normalized judge and attorney profiles via UniCourt's JudgeAnalytics and AttorneyAnalytics APIs
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 access token via UniCourt's OAuth2 client-credentials flow
Call JudgeAnalytics.search_normalized_judges(q='name:(...)') with a structured query string to find a normalized judge record and its norm_judge_id
Call AttorneyAnalytics.search_normalized_attorneys(q='name:(...)', page_number=1) to find normalized attorney records and their norm_attorney_id values
Use the returned norm_judge_id/norm_attorney_id as stable keys for deeper analytics (case history, rulings, litigation patterns) tied to that entity, rather than re-searching by name each time
Paginate search_normalized_attorneys results with page_number when a name query returns more matches than fit on one page
Cache normalized IDs locally, since common-name searches can return multiple candidate matches requiring your own disambiguation logic
Known gotchas
Search queries use a structured query-string syntax (e.g. name:(LAST FIRST)) rather than simple free-text parameters — malformed query syntax returns empty results rather than an error, which can look like missing data
Common names return multiple normalized candidates; the API does not auto-resolve ambiguity
Normalized judge/attorney profiles are UniCourt's own entity-resolution layer on top of raw filings — a person can be missing a normalized profile even though underlying case data referencing them already exists in the Court Data API
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?