Authenticate by POSTing to https://www.docketalarm.com/api/v1/login/ with your username and password to obtain a login token
Include the token as the login parameter in subsequent API requests
POST or GET to https://www.docketalarm.com/api/v1/search/ with parameters including query (keyword string), party_name, and optionally court to scope the search
Parse the returned results array; each item includes the case title, court, docket number, and a case URL for fetching the full docket
To retrieve a full docket's entry list, call the docket-specific endpoint with the court and docket number obtained from the search results
Known gotchas
The /search/ endpoint queries Docket Alarm's internal index, which may lag real-time court filings by hours; use /searchdirect/ for real-time court queries at the cost of fewer filtering options
Usage is metered; high-volume searches consume API credits quickly — implement result caching to avoid re-querying known cases
Search queries must be URL-encoded; boolean operators and phrase-matching syntax follow Docket Alarm's own query language, not standard Lucene syntax
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp