Enumerations & Reference
This reference guide provides a comprehensive list of static values, status types, and logic used across the TruRisk AI module. Use these values to validate your API requests and handle response logic correctly.
AI Verdicts (verdict)
The verdict field represents the AI Agent's assessment of an entity match. These are found in the response of the Screening and Retrieval endpoints.
| Value | Label | Description |
|---|---|---|
true_positive | True Positive | High confidence that the entity is the same as the record found. |
false_positive | False Positive | The AI has determined the entity is not a match to the found record. |
true_negative | True Negative | No significant matches were found in any AML databases. |
potential_match | Potential Match | Similarity exists, but parameters are insufficient for full confidence. |
uncertain | Uncertain | The AI requires more data or human intervention to make a determination. |
pending | Pending | AI analysis is currently in progress. |
Verdict outcomes and confidence are directly dependent on the completeness and quality of the input profile data provided at screening time. More comprehensive identifiers produce stronger identity resolution and higher-confidence determinations.
Match Score & Confidence
match_score reflects the strength of identity resolution behind a result—how closely the submitted identity attributes align with the matched record—rather than simple name similarity. It is what allows TruRisk to distinguish a confirmed match from an unrelated record that merely shares a name.
Analyst Decisions (analyst_decision)
After the AI provides a verdict, a human analyst typically reviews the result. This field tracks the human-in-the-loop decision.
| Value | Description |
|---|---|
Confirmed | The analyst agrees with the AI's verdict. |
Declined | The analyst overrides the AI's verdict based on manual review. |
null / Empty | The record is still awaiting manual review (Pending). |
Screening Statuses (status)
The lifecycle status of a TruRisk customer record.
| Value | Description |
|---|---|
COMPLETED | The screening and AI narrative generation are finished. |
Pending | The entity is currently being screened or analyzed by the AI. |
in-progress | Active processing is occurring. |
Entity Types (entity_type)
TruRisk supports various entity classifications. Note that some fields are dependent on specific entity types.
- Person: Standard individual screening.
- Company: Corporate entity screening.
- Vessel: Required to enable
imo_numbervalidation. Use exactlyVesselinentity_type. - Aircraft: Required to enable
tail_numbervalidation. Use exactlyAircraftinentity_type. - Organization: Non-corporate group screening.
- Crypto_Wallet: Digital asset wallet screening.
Key Drivers (key_drivers)
These are tags returned by the AI to explain which specific input fields triggered a match. Common drivers include:
Adverse Mediabirth_incorporation_dateidentification_numbernationalitysibling/parent/spouse- Sanctions list match
- Adverse media severity
Technical Appendix: Error Codes
| Code | Type | Logic |
|---|---|---|
400 | Bad Request | Missing mandatory field (e.g., name) or validation error. |
400 | Validation Error | Attempting to provide two identifiers (e.g., imo_number and tail_number) at once. |
401 | Unauthorized | Missing or invalid Bearer Token. |
403 | Forbidden | Organization does not have the TruRisk module enabled in Configuration. |
404 | Not Found | customer_id does not exist. |