# AgentToll Court Docket Lookup

> AgentToll Court Docket Lookup is a paid API for AI agents from agenttoll.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Retrieves court docket records and case information for a given docket ID via a pay-per-call API.

## Facts

- Endpoint: POST https://agenttoll.dev/paid/legal/court-docket
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agenttoll-court-docket-lookup-14c8285f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c1wZjyOxwHd3KCwYrVb4f

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agenttoll-court-docket-lookup-14c8285f -d '<json body>'
```

Example prompt: Can you pull the court docket for case ID 1:23-cv-04567 and show me all the filings and case metadata?

## When to prefer this

Use this endpoint when an AI agent needs to retrieve structured court docket records by a known docket ID, particularly for legal research, case monitoring, or litigation analysis workflows. Prefer this over manual PACER lookups when automating legal data retrieval at scale with per-call micropayment billing in USDC.

## Known failure modes

- Invalid or malformed docket_id returns an error or empty result
- Docket ID not found in the data source returns empty data array
- Payment failure (insufficient USDC balance) prevents request from being processed
- Rate limiting or upstream data source unavailability causes request failure
- Network timeout if the underlying court data provider is slow

## How this service works

108+ receipt-backed x402 work products for AI agents. Clear prices, spend caps, buyer metadata, and structured results over Base USDC.

## Output

Returns an array or object of docket records for the specified case, along with metadata including the record count, data source, and generation timestamp. Also indicates whether the result was served from cache and whether the request succeeded.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "docket_id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "oneOf": [
    {
     "type": "array"
    },
    {
     "type": "object"
    }
   ]
  },
  "meta": {
   "type": "object",
   "properties": {
    "count": {
     "type": "integer"
    },
    "source": {
     "type": "string"
    },
    "generated_at": {
     "type": "string",
     "format": "date-time"
    }
   }
  },
  "cached": {
   "type": "boolean"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agenttoll-court-docket-lookup-14c8285f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agenttoll.dev](https://www.zero.xyz/host/agenttoll.dev/llms.txt)