Litigation Monitoring + Case Intelligence

A qualified litigation monitoring + case intelligence intelligence feed for teams that need procurement signals before manual search catches up. Monitors CourtListener API, CourtListener bulk data and returns buyer-ready records with source evidence.

Who this is for

Procurement, sales, partnerships, compliance, and research teams use this actor when they need a focused litigation monitoring + case intelligence feed instead of a broad generic scraper.

Buyer outcomes

• Find relevant litigation monitoring + case intelligence records faster with normalized source evidence and match context.
• Prioritize review using scores, confidence, source URLs, and buyer-ready summary fields.
• Route new or changed records into recurring workflows through saved inputs, schedules, and alerts.

Sources monitored

CourtListener API, CourtListener bulk data

Inputs

• sourceMode: use sample for the default Store test, startUrls for URL-backed runs, or another supported source mode when configured.
• startUrls: optional public URLs with a working small default/prefill for URL-backed smoke runs.
• sourceIds: approved source identifiers to keep runs scoped to known public data sources.
• maxItems: bounded result limit; the default is intentionally small for first-run validation.
• sinceLastRun: return only new or changed records when scheduled delta mode is enabled.
• watchlistTerms: buyer keywords, companies, products, places, or risk terms used for monitoring context.
• webhookUrl: optional completion or alert destination for recurring workflows.
• outputMode: use sample records for Store validation or buyer-ready records for production runs.

Outputs

The actor returns buyer-ready records with source attribution, match context, and normalized fields for review or downstream routing.

• title: Buyer-readable opportunity or record title.
• source_url: Direct source URL for review and audit.
• source_id: Source identifier used to trace where the record came from.
• buyer_name: Public buyer, authority, issuer, or organization.
• country: Normalized field for filtering, routing, or downstream review.
• published_at: Normalized field for filtering, routing, or downstream review.
• deadline: Submission or response deadline when available.
• cpv_codes: Normalized field for filtering, routing, or downstream review.
• estimated_value: Normalized field for filtering, routing, or downstream review.
• currency: Normalized field for filtering, routing, or downstream review.
• match_reason: Plain-language reason this record matched the actor focus.
• evidence: Normalized field for filtering, routing, or downstream review.
• dedupe_key: Normalized field for filtering, routing, or downstream review.
• scraped_at: Normalized field for filtering, routing, or downstream review.

Pricing

This actor uses Apify pay-per-event pricing. Current public listing guidance: $29-$49 / 1,000 launch validation records until public data proof is complete. Charges are tied to buyer-visible value events such as change-alert, change-alert, change-alert. Small validation runs are supported so you can inspect output before scaling a schedule.

• change-alert: Charge when Litigation Monitoring + Case Intelligence produces Record Saved. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• change-alert: Charge when Litigation Monitoring + Case Intelligence produces Enriched Record. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• change-alert: Charge when Litigation Monitoring + Case Intelligence produces Report Generated. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• first-run-cap: Recommended first run budget cap. Typical price: $3.820. Start with the default small run, inspect the dataset, then raise maxItems or schedule recurring runs.

API example

curl -X POST "https://api.apify.com/v2/acts/YOUR_USERNAME~courtlistener-litigation-intelligence/runs" \
+  -H "Authorization: Bearer $APIFY_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"maxItems":10,"sourceIds":["COURTLISTENER-API","COURTLISTENER-BULK"],"includeSourceUrls":true,"includeMatchReasons":true,"outputMode":"buyer-ready-records"}'

Recommended first run

{
    "maxItems": 10,
    "sourceIds": [
        "COURTLISTENER-API",
        "COURTLISTENER-BULK"
    ],
    "includeSourceUrls": true,
    "includeMatchReasons": true,
    "outputMode": "buyer-ready-records"
}

Sample output

Review a static sample output record before running the actor: https://zentraforge.store/external/actor-review/samples/courtlistener-litigation-intelligence.json

Recommended public tasks

[
    {
        "name": "First 10 qualified records",
        "description": "Low-cost validation run for checking output quality and source fit.",
        "input": {
            "maxItems": 10,
            "sourceIds": [
                "COURTLISTENER-API",
                "COURTLISTENER-BULK"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "courtlistener-litigation-intelligence"
        }
    },
    {
        "name": "Daily monitoring feed",
        "description": "Recurring small batch for new buyer-value records.",
        "schedule": "Daily during local business hours",
        "input": {
            "maxItems": 25,
            "sourceIds": [
                "COURTLISTENER-API",
                "COURTLISTENER-BULK"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "courtlistener-litigation-intelligence"
        }
    }
]

Use cases

• Track new litigation monitoring + case intelligence opportunities without checking each source manually.
• Route qualified records into CRM, spreadsheets, or internal review queues.
• Monitor deadlines, buyer names, source links, and match reasons for faster triage.
• Schedule recurring runs to catch new signals while keeping first-run costs low.

Trust and compliance

• Uses CourtListener API, CourtListener bulk data.
• Designed for public-source procurement and data-intelligence workflows.
• Keeps source URLs and source identifiers in output records for auditability.
• Does not require private credentials unless a source is explicitly configured for approved authenticated access.

Limitations

• Results depend on public-source availability, source uptime, and source update cadence.
• Public sources can revise records after publication; rerun scheduled tasks for fresh evidence.
• Scores and match reasons are decision-support signals, not legal, financial, procurement, or compliance advice.
• Large production runs can cost more than the default smoke run; start small, inspect output, then scale schedules.

FAQ

Can I run this without URLs? Yes. The default sample mode is designed to succeed without user-supplied URLs, and URL-backed runs can use startUrls when needed.

Can I schedule it? Yes. Use sinceLastRun, watchlistTerms, and optional webhookUrl to turn the actor into a recurring alert or report workflow.

How do I verify value before scaling? Run the recommended first-run input, review the sample output fields, then increase maxItems or schedule recurring runs after the dataset matches your use case.