Live Risk API Overview

The SESAMm Live Risk API allows clients to programmatically generate and retrieve company-level risk assessments. Designed for seamless integration into enterprise workflows, the API supports high-volume use cases such as private assets rating and due diligence, Know Your Customer (KYC) for businesses, automated underwriting and questionnaires, and counterparty reputational risk checks.

1. Product Description

The Live Risk API enables the generation of risk profiles for both public and private companies globally. By leveraging SESAMm’s artificial intelligence engine, the API processes large-scale web and news data to identify potential controversies and reputational risks associated with a specific entity (company or infrastructure project).

2. Coverage and Performance

  • Universe: Access to SESAMm’s standard coverage universe, with the capability to generate on-the-fly risk assessments for up to 600 million companies.
  • Latency: Live entity creation and risk assessment generation are typically completed in under one minute per request.
  • Scale: Built for system-to-system automation and large-scale batch processing.

3. Input Requirements

To initiate a risk assessment, the API requires specific identifiers to ensure accurate entity matching.

  • Batch Capacity: Supports up to 150 legal identifiers per individual request.
  • Supported Identifiers:
    • Legal Entity Identifier (LEI)
    • International Securities Identification Number (ISIN)
    • Multiple local legal identifiers, including country-specific ones
    • Data Universal Numbering System (DUNS), where available
    • Company Name and Country (fallback for entities without global identifiers)

4. Output Format

The API delivers results in a structured JSON response, optimized for direct ingestion by internal risk platforms, CRMs, or data lakes.

  • Aggregated Scores: Provides high-level company risk signals based on the configured analysis type.
  • Supporting Evidence: Depending on the client’s specific configuration, responses include metadata and links to relevant sources.

5. Typical Output Fields

While the exact schema is subject to contractual configuration, the standard API response includes core fields designed to provide a comprehensive risk summary.

Core Fields

  • company_name: The name of the entity under analysis.
  • risk_name: The specific category of risk identified (e.g., sub-categories related to Reputational, Environmental, Social, Governance, AML risk etc.).
  • justification: A detailed qualitative explanation justifying the risk level identified by the AI.
  • risk_score: The numerical or categorical score representing the intensity of the risk.
  • supporting_cases: A nested list of individual events or articles supporting the assessment.

Supporting Case Sub-fields

The sub-fields within supporting_cases are defined and configured according to the client’s specific needs and agreement. These can include, depending on the configuration:

  • title: The name or headline of the identified risk event.
  • summary: A concise description of the risk context.
  • dashboard_url: A direct link to the full analysis within the SESAMm platform.
  • start_date: The earliest detected instance of the risk event.
  • last_activity: The date of the most recent detected update regarding the event.
  • score: The calculated severity or intensity score for the specific case.
  • top_urls: Direct links to the primary web sources identifying the risk.

6. Customization and Alignment

The Live Risk API can be tailored to meet specific institutional requirements:

  • Taxonomy: Risk categories can be mapped to align with a client’s internal risk framework or regulatory requirements.
  • Thresholds: Risk scoring and alerting thresholds are customizable upon request to filter for specific levels of materiality.

7. Important Technical Clarifications

  • Content Delivery: The API delivers risk scores and metadata; it does not deliver raw article content or full-text scrapes.
  • Configuration Dependency: The exact depth of data, field availability, and response structure are defined by the contractual configuration in the applicable Purchase Order.