Authenticate to CourtListener using 'Authorization: Token YOUR_TOKEN'
Resolve the CourtListener docket ID for your case by querying GET https://www.courtlistener.com/api/rest/v4/dockets/?pacer_case_id=YOUR_PACER_CASE_ID
POST to https://www.courtlistener.com/api/rest/v4/docket-alerts/ with a JSON body containing the docket URL or ID and the desired alert_type (1 for active subscription, 0 for inactive)
To also receive alerts on new documents within docket entries, use alert_type=r (RECAP-level) rather than alert_type=d (docket-level only)
Manage alerts by sending a DELETE or PATCH request to /api/rest/v4/docket-alerts/ALERT_ID/ to remove or modify the subscription
Known gotchas
Docket alerts are limited per account tier; review your CourtListener membership level to understand the maximum number of simultaneous active alerts
Alert delivery can come via email or webhook; configure webhooks for machine-readable events rather than relying on email parsing
If the underlying PACER case is sealed or restricted, CourtListener may not receive new entries even if a docket alert is active
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