AgentSkillsCN

didit-aml-screening

集成Didit AML筛查独立API,对个人或公司进行全球观察名单筛查。当用户希望进行AML检查、筛查制裁名单、核查PEP状态、检测不良媒体、实施KYC/AML合规、筛查OFAC/联合国/欧盟观察名单、计算风险评分,或使用Didit进行反洗钱筛查时使用此功能。支持1300+个数据库、模糊姓名匹配、可配置的评分权重,以及持续监测功能。

SKILL.md
--- frontmatter
name: didit-aml-screening
description: >
  Integrate Didit AML Screening standalone API to screen individuals or companies against
  global watchlists. Use when the user wants to perform AML checks, screen against sanctions
  lists, check PEP status, detect adverse media, implement KYC/AML compliance, screen against
  OFAC/UN/EU watchlists, calculate risk scores, or perform anti-money laundering screening
  using Didit. Supports 1300+ databases, fuzzy name matching, configurable scoring weights,
  and continuous monitoring.
version: 1.0.0
metadata:
  openclaw:
    requires:
      env:
        - DIDIT_API_KEY
    primaryEnv: DIDIT_API_KEY
    emoji: "🛡️"
    homepage: https://docs.didit.me

Didit AML Screening API

Overview

Screens individuals or companies against 1,300+ global watchlists and high-risk databases in real-time. Uses a two-score system: Match Score (identity confidence) and Risk Score (threat level).

Key constraints:

  • full_name is the only required field
  • Supports entity_type: "person" (default) or "company"
  • Document number acts as a "Golden Key" for definitive matching
  • All weight parameters must sum to 100

Coverage: OFAC SDN, UN, EU, HM Treasury, Interpol, FBI, 170+ national sanction lists, PEP Levels 1-4, 50,000+ adverse media sources, financial crime databases.

Scoring system:

  1. Match Score (0-100): Is this the same person? → classifies hits as False Positive or Unreviewed
  2. Risk Score (0-100): How risky is this entity? → determines final AML status

API Reference: https://docs.didit.me/reference/aml-screening-standalone-api


Authentication

All requests require x-api-key header. Get your key from Didit Business Console → API & Webhooks.


Endpoint

code
POST https://verification.didit.me/v3/aml/

Headers

HeaderValueRequired
x-api-keyYour API keyYes
Content-Typeapplication/jsonYes

Body (JSON)

ParameterTypeRequiredDefaultDescription
full_namestringYesFull name of person or entity
date_of_birthstringNoDOB in YYYY-MM-DD format
nationalitystringNoISO country code (alpha-2 or alpha-3)
document_numberstringNoID document number ("Golden Key")
entity_typestringNo"person""person" or "company"
aml_name_weightintegerNo60Name weight in match score (0-100)
aml_dob_weightintegerNo25DOB weight in match score (0-100)
aml_country_weightintegerNo15Country weight in match score (0-100)
aml_match_score_thresholdintegerNo93Below = False Positive, at/above = Unreviewed
save_api_requestbooleanNotrueSave in Business Console
vendor_datastringNoYour identifier for session tracking

Example

python
import requests

response = requests.post(
    "https://verification.didit.me/v3/aml/",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "full_name": "John Smith",
        "date_of_birth": "1985-03-15",
        "nationality": "US",
        "document_number": "AB1234567",
        "entity_type": "person",
    },
)
print(response.json())
typescript
const response = await fetch("https://verification.didit.me/v3/aml/", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    full_name: "John Smith",
    date_of_birth: "1985-03-15",
    nationality: "US",
  }),
});

Response (200 OK)

json
{
  "request_id": "a1b2c3d4-...",
  "aml": {
    "status": "Approved",
    "total_hits": 2,
    "score": 45.5,
    "hits": [
      {
        "id": "hit-uuid",
        "caption": "John Smith",
        "match_score": 85,
        "risk_score": 45.5,
        "review_status": "False Positive",
        "datasets": ["PEP"],
        "properties": {"name": ["John Smith"], "country": ["US"]},
        "score_breakdown": {
          "name_score": 95, "name_weight": 60,
          "dob_score": 100, "dob_weight": 25,
          "country_score": 100, "country_weight": 15
        },
        "risk_view": {
          "categories": {"score": 55, "risk_level": "High"},
          "countries": {"score": 23, "risk_level": "Low"},
          "crimes": {"score": 0, "risk_level": "Low"}
        }
      }
    ],
    "screened_data": {
      "full_name": "John Smith",
      "date_of_birth": "1985-03-15",
      "nationality": "US",
      "document_number": "AB1234567"
    },
    "warnings": []
  }
}

Match Score System

Formula: (Name × W1) + (DOB × W2) + (Country × W3)

ComponentDefault WeightAlgorithm
Name60%RapidFuzz WRatio — handles typos, word order, middle name variations
DOB25%Exact=100%, Year-only=100%, Same year diff date=50%, Mismatch=-100%
Country15%Exact=100%, Mismatch=-50%, Missing=0%. Auto-converts ISO codes

Document Number "Golden Key":

ScenarioEffect
Same type, same valueOverride score to 100
Different type or one missingKeep base score (neutral)
Same type, different value-50 point penalty

Classification: Score < threshold (default 93) → False Positive. Score >= threshold → Unreviewed.

When data is missing, remaining weights are re-normalized. E.g., name-only → name weight becomes 100%.


Risk Score System

Formula: (Country × 0.30) + (Category × 0.50) + (Criminal × 0.20)

Final AML Status (from highest risk score among non-FP hits):

Highest Risk ScoreStatus
Below 80 (default)Approved
Between 80-100In Review
Above 100Declined
All False PositivesApproved

Category scores (50% weight):

CategoryScore
Sanctions / PEP Level 1100
Warnings & Regulatory95
PEP Level 2 / Insolvency80
Adverse Media60
PEP Level 4 / Businessperson55

Status Values & Handling

StatusMeaningAction
"Approved"No significant matches or all False PositivesSafe to proceed
"In Review"Matches found with moderate riskManual compliance review needed
"Rejected"High-risk matches confirmedBlock or escalate per your policy
"Not Started"Screening not yet performedCheck for missing data

Error Responses

CodeMeaningAction
400Invalid request bodyCheck full_name and parameter formats
401Invalid API keyVerify x-api-key header
403Insufficient creditsCheck credits in Business Console

Warning Tags

TagDescription
POSSIBLE_MATCH_FOUNDPotential watchlist matches requiring review
COULD_NOT_PERFORM_AML_SCREENINGMissing KYC data. Provide full name, DOB, nationality, document number

Response Field Reference

Hit Object

FieldTypeDescription
match_scoreinteger0-100 identity confidence score
risk_scorefloat0-100 threat level score
review_statusstring"False Positive", "Unreviewed", "Confirmed Match", "Inconclusive"
datasetsarraye.g. ["Sanctions"], ["PEP"], ["Adverse Media"]
pep_matchesarrayPEP match details
sanction_matchesarraySanction match details
adverse_media_matchesarray{headline, summary, source_url, sentiment_score, adverse_keywords}
linked_entitiesarrayRelated persons/entities
first_seen / last_seenstringISO 8601 timestamps

Adverse media sentiment: -1 = slightly negative, -2 = moderately, -3 = highly negative.


Continuous Monitoring

Available on Pro plan. Automatically included for all AML-screened sessions.

  • Daily automated re-screening against updated watchlists
  • New hits → session status updated to "In Review" or "Declined" based on thresholds
  • Real-time webhook notifications on status changes
  • Zero additional integration — uses same thresholds from workflow config

Common Workflows

Basic AML Check

code
1. POST /v3/aml/ → {"full_name": "John Smith", "nationality": "US"}
2. If "Approved" → no significant watchlist matches
   If "In Review" → review hits[].datasets, hits[].risk_view for details
   If "Rejected" → block user, check hits for sanctions/PEP details

Comprehensive KYC + AML

code
1. POST /v3/id-verification/ → extract name, DOB, nationality, document number
2. POST /v3/aml/ → screen extracted data with all fields populated
3. More data = higher match accuracy = fewer false positives