Run compliance screening from the cabinet, the API or an AI agent.
The Compliance Platform training deck shows how to perform sanctions, PEP and export-control screening across all three surfaces — the web cabinet, the REST API and the MCP-native AI Assistant — with worked, real-world web-agent scenarios.
Two parts: the AI Assistant guide and web-agent scenarios
The training deck is built in two parts. The first is a guide to the Compliance Platform AI Assistant — how an MCP-native assistant queries the same screening engine the cabinet uses, and why a grounded, source-linked answer is different from a chatbot's guess. The second is a set of worked web-agent scenarios: concrete, step-by-step walkthroughs of real compliance tasks run end to end.
The AI Assistant
Compliance Platform exposes an MCP connector, so AI agents — Claude, ChatGPT or a custom agent — can run screening operations natively. The Assistant queries indexed sanctions, PEP and export-control data only; it does not invent regulations. Every answer comes back grounded, cited and reproducible, the same way a cabinet result does.
Web-agent scenarios
The scenario chapters walk through compliance tasks as an agent actually performs them — entity and UBO screening, TARIC classification, ISO 20022 payment screening, export-control candidate checks — showing the inputs, the tool calls and the evidence that lands in the case.
Why three surfaces matter
A compliance reviewer works in the web cabinet. An engineer integrates entitled REST API workflows. An AI agent calls the plan-included MCP connector. All three share the same core screening and relevant profiles from a catalogue of 150+ official sources; access, persistence and output remain channel-specific.
Who the training is for
Compliance officers and reviewers learning the cabinet, engineers integrating the API, and teams adopting AI-assisted compliance workflows. The deck is practical: it is built to be followed, not just read.