EU Parliament Monitor — API Documentation - v0.8.6
    Preparing search index...

    Interface ThreatAssessmentInput

    Input data for political threat assessment functions.

    Named ThreatAssessmentInput to avoid collision with the separate ArticleData interface in article strategy modules. Mirrors the structure of MCP-fetched data used throughout the pipeline.

    interface ThreatAssessmentInput {
        votingRecords?: readonly unknown[];
        coalitionData?: readonly unknown[];
        mepInfluence?: readonly unknown[];
        procedures?: readonly unknown[];
        anomalies?: readonly unknown[];
        votingAnomalies?: readonly unknown[];
        questions?: readonly unknown[];
        committees?: readonly unknown[];
        feedData?: Record<string, unknown>;
    }
    Index

    Properties

    votingRecords? coalitionData? mepInfluence? procedures? anomalies? votingAnomalies? questions? committees? feedData?

    Properties

    votingRecords?: readonly unknown[]

    Voting records from plenary sessions

    coalitionData?: readonly unknown[]

    Coalition dynamics data

    mepInfluence?: readonly unknown[]

    MEP influence scores

    procedures?: readonly unknown[]

    Legislative procedure data

    anomalies?: readonly unknown[]

    Voting anomaly intelligence.

    The existing MCP fetch pipeline and article strategies expose voting anomalies under the field name anomalies. Both anomalies and the legacy votingAnomalies alias are accepted; anomalies takes precedence.

    votingAnomalies?: readonly unknown[]

    Use anomalies instead — kept for backward compatibility

    questions?: readonly unknown[]

    Parliamentary questions

    committees?: readonly unknown[]

    Committee data

    feedData?: Record<string, unknown>

    Feed data (adopted texts, procedures, MEPs)

    Settings

    Member Visibility

    On This Page

    Properties