timzinin-com Litigation Check API

openapi: 3.2.0
info:
  title: Zinin M2M Hub Litigation Check API
  description: Pay-per-call data & tool APIs
  version: 1.0.0
  x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Litigation Check
paths:
  /api/litigation-check:
    post:
      summary: Litigation Check
      description: Screen a company for litigation history across US federal dockets (CourtListener), UK case law and Polish court judgments. Keyless, one row per company x jurisdiction, with the true case count and links to the source records.
      operationId: call_litigation_check
      x-payment-info:
        price:
          mode: fixed
          currency: USD
          amount: '0.030000'
        protocols:
        - x402: {}
        network: eip155:8453
        payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
        asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              title: Litigation Check input
              type: object
              schemaVersion: 1
              properties:
                companies:
                  title: Companies
                  type: array
                  description: Legal names of companies / counterparties to screen for litigation history. One row is produced per company per selected jurisdiction, up to your run's maximum charge (maxTotalChargeUsd) — if that budget runs out early, the remaining pairs are skipped and a final row explains why. Use the full legal name for the cleanest match (e.g. "Tesla, Inc." rather than "Tesla").
                  maxItems: 20
                  editor: stringList
                  prefill:
                  - Tesla, Inc.
                jurisdictions:
                  title: Jurisdictions
                  type: array
                  description: 'Which court systems to check: US, UK, PL. US = federal PACER dockets via CourtListener (structural party-name search). UK = England & Wales / UK Supreme Court case law (structural party-name search, same guarantee as US). PL = Poland SAOS full-text judgment search — a keyword mention, not a confirmed party (see README). Any other code is returned as a free, graceful "unsupported jurisdiction" row rather than rejected — see the README for what''s excluded and why.'
                  maxItems: 3
                  editor: stringList
                  prefill:
                  - US
                maxCasesPerRow:
                  title: Max cases per row
                  type: integer
                  description: How many individual cases to list per company x jurisdiction row. caseCount reports the true total matched for US/PL (approximate above ~2000 matches — CourtListener's own count estimate), even when fewer are listed here; for UK it can be a lower bound when the output row's partial field is true (see README).
                  default: 20
                  prefill: 10
                  minimum: 1
                  maximum: 50
                maxConcurrency:
                  title: Max concurrency
                  type: integer
                  description: How many companies to check in parallel. Each company's selected jurisdictions are always fetched in parallel with each other regardless of this setting.
                  default: 2
                  minimum: 1
                  maximum: 2
              required:
              - companies
      responses:
        '200':
          description: Actor run succeeded and payment settled
          content:
            application/json:
              schema:
                type: object
                properties:
                  results:
                    type: array
                    items:
                      type: object
                    description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
                  meta:
                    type: object
                    properties:
                      run_ms:
                        type: integer
                        description: Actor run duration in milliseconds
                      item_count:
                        type: integer
                        description: len(results)
                      settled:
                        type: boolean
                        description: Whether the x402 payment was confirmed settled by the facilitator
                      transaction:
                        type:
                        - string
                        - 'null'
                        description: On-chain settlement transaction hash, null if unsettled
                    required:
                    - run_ms
                    - item_count
                    - settled
                    - transaction
                required:
                - results
                - meta
        '400':
          description: Malformed PAYMENT-SIGNATURE header or request body
        '402':
          description: Payment required or invalid — see PAYMENT-REQUIRED header
        '409':
          description: Payment payload already used
        '502':
          description: Actor run failed
        '504':
          description: Actor run timed out
      tags:
      - Litigation Check