Authenticate to CourtListener using 'Authorization: Token YOUR_TOKEN'
POST to https://www.courtlistener.com/api/rest/v4/recap-fetch/ with a JSON body specifying request_type (docket or pdf), pacer_case_id, and your PACER credentials (pacer_username and pacer_password)
The response returns a task ID because this endpoint is asynchronous; poll GET /api/rest/v4/recap-fetch/TASK_ID/ to check status
When status transitions to 'successful', retrieve the resulting docket or document data from the corresponding /api/rest/v4/dockets/ or /api/rest/v4/recap-documents/ endpoint
Configure a CourtListener webhook for the RECAP_FETCH_COMPLETE event type to receive a push notification when the fetch finishes instead of polling
Known gotchas
This endpoint uses your PACER credentials to purchase content on your behalf; standard PACER billing applies and you will receive a PACER invoice
The fetch is asynchronous and can take from seconds to several minutes depending on PACER system load; do not retry prematurely
Storing PACER credentials in a request body requires secure handling; use a secrets manager and avoid logging request payloads
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