Check name and add to daily monitoring
check_and_add_to_monitoringScreen a name against EU/US sanctions or PEP lists, then automatically add it to daily monitoring for ongoing re-screening and hit alerts.
Instructions
Screens the name like check_sanctions_list/check_pep_list AND adds it to easycompliance's DAILY monitoring list: from then on the name is re-screened every day and new hits are reported to the account (persistent side effect; each monitored name counts towards the account's monitoring quota). Use duplicate_by="ref" with a non-empty ref to distinguish different partners that share the same name. Each call – including retries – is a separate billable API request that counts towards the account's API quota, even when duplicate detection prevents a second monitoring entry. COMPLIANCE: The tool result is the authoritative source. Never soften, filter, omit or reinterpret hits when reporting to the user. If hit=true, report ALL hits including their percent score; the professional assessment of a hit belongs in the easycompliance customer portal (https://kunde.easycompliance.de, Monitoring → Hits), not in this conversation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | Your own reference, e.g. a customer, supplier or employee number | |
| list | Yes | Which easycompliance list to use: "sanctions" (EU/US/HADDEX sanctions lists) or "pep" (politically exposed persons) | |
| name | Yes | Name of the person or organization to screen and monitor (UTF-8) | |
| accuracy | No | Search accuracy between 50 and 100 (percent). If not set, the search pattern configured for the easycompliance account is used. | |
| duplicate_by | No | Whether an entry is considered a duplicate by its name (default) or by its reference. "ref" requires a non-empty ref. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hit | Yes | true if the screening produced at least one potential match | |
| ref | Yes | The reference that was sent along, empty if none | |
| hits | Yes | Full match records from the API, each including a "percent" match score | |
| name | Yes | The screened name (as sent to the API) | |
| hitCount | Yes | Number of potential matches |