timzinin-com Counterparty Risk Rollup API

openapi: 3.2.0
info:
  title: Zinin M2M Hub Counterparty Risk Rollup 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: Counterparty Risk Rollup
paths:
  /api/counterparty-risk-rollup:
    post:
      summary: Counterparty Risk Rollup
      description: 'Screen a counterparty in one call: OFAC + EU sanctions match, GLEIF legal-entity registry, litigation history (US/UK/PL) and a hiring signal from public ATS boards, combined into one row per company with a documented risk score. Keyless sources only.'
      operationId: call_counterparty_risk_rollup
      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: Counterparty Risk Rollup input
              type: object
              schemaVersion: 1
              properties:
                companies:
                  title: Companies
                  type: array
                  description: Company legal names to assess, one per row (a Legal Entity Identifier is also accepted for the registry check). One dataset row comes out per company, combining every check you selected below.
                  maxItems: 20
                  editor: stringList
                  prefill:
                  - Siemens AG
                checks:
                  title: Checks to run
                  type: array
                  description: Which of the four checks to run per company. Sanctions and registry are fast (shared cached list + one API call); litigation and hiring each add one more API call per company.
                  editor: select
                  items:
                    type: string
                    enum:
                    - sanctions
                    - registry
                    - litigation
                    - hiring
                    enumTitles:
                    - Sanctions (OFAC + EU)
                    - Legal-entity registry (GLEIF)
                    - Litigation history (US/UK/PL)
                    - Hiring signal (Greenhouse/Lever/Ashby)
                  maxItems: 4
                  default:
                  - sanctions
                  - registry
                  prefill:
                  - sanctions
                  - registry
                jurisdictionHint:
                  title: Jurisdiction hint (2-letter code)
                  type: string
                  description: Optional ISO country code, e.g. "GB", "DE", "PL". Narrows the registry lookup to that country and picks which litigation source is queried (GB/UK -> UK case law, PL -> Poland SAOS, anything else -> US CourtListener, the default). "UK" is accepted as a synonym for "GB" everywhere — it is normalized to the ISO code "GB" before it reaches the registry (GLEIF) lookup, since GLEIF itself only recognizes "GB".
                  default: ''
                  editor: textfield
                  prefill: GB
                maxConcurrency:
                  title: Max concurrency
                  type: integer
                  description: How many companies to assess in parallel.
                  default: 3
                  minimum: 1
                  maximum: 8
              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:
      - Counterparty Risk Rollup