Skip to main content
AI Agents

Your stack or ours: compliance agents without a migration

You do not need to replace your case system to get an AI agent. Cogentic reads the tools you run, or supplies KYC, monitoring, sanctions and wallet intelligence itself, one layer at a time.

  • Cogentic Team
  • 3 min read

In short

  1. 1Compliance agents do not require you to move your cases or procedures into a new system. Cogentic connects the tools you already run.
  2. 2Migrations add cost, run two systems at once and grow the fragmentation they were meant to fix.
  3. 3Keep your providers, use Cogentic's KYC, KYT, sanctions and wallet intelligence or combine the two, one capability at a time.

The fork in compliance AI

Compliance teams know how a migration goes. Vendor onboarding, field mapping between the old case system and the new one, SOPs rewritten in the new tool's vocabulary and analysts retrained on an unfamiliar screen. The new system may be better. The migration is still the project, and it can sit between your team and the benefit for a long time.

Compliance AI offers the same fork. One route asks you to move your cases and procedures into the vendor's system. The other puts the agent where your data already lives, and gives you a choice about which layers you keep.

What a migration costs

The visible costs are licences, integration fees and training. The hidden costs are larger.

  • Two systems run at once. During cutover, neither is fully the record, which makes the audit trail harder to read exactly when you need it.
  • Procedure knowledge gets lost in translation. Years of SOP wording and case taxonomy have to be rebuilt in a new tool's terms.
  • Fragmentation grows. Your screening, chain analytics and identity providers stay in place and there is now another system to open.

Work where the data already lives

An agent that works inside your stack reads wallet attribution from Chainalysis, TRM Labs or Elliptic where you already hold it. It reads Sumsub and ComplyAdvantage results as your providers returned them and wallet and transfer activity from Fireblocks. It reads your case system and CRM in place, and it takes alerts, customers and transfers from your own systems through a REST API and webhooks.

Each finding keeps the provider it came from. Your team keeps its SOPs and its vocabulary, and the agent applies your procedures on top. Nothing is copied out by hand and nothing needs migrating.

Your stack or ours, one capability at a time

Keeping everything is one option. Cogentic also supplies its own customer verification, transaction monitoring, sanctions screening and wallet intelligence. You can keep your providers, use Cogentic's managed capabilities or combine the two, and you move one capability at a time.

The investigation runs the same way either way. Whichever provider supplied a result, it lands in the same case with its source and the time it was produced.

LayerIf you keep your providerIf you use Cogentic's
Customer verification (KYC)Results land in the same customer record as any other sourceResults land in the same customer record, read the same way by the investigation
Transaction monitoring (KYT)Alerts from your system open a case with the same context and procedureCogentic's alerts open a case the same way
Sanctions screeningYour provider's result sits in the case with the list it was checked against and the time of the checkThe same result, list and time sit in the case
Wallet intelligenceYour own analytics contracts supply attribution and exposureCogentic's managed access supplies attribution and exposure
How each layer works under either choice

Why changing one layer at a time matters

A business can start by connecting what it has. When a contract ends or a layer underperforms, it can take Cogentic's capability for that layer without redesigning the workflow or retraining the team. The procedure, the case record and the analyst's screen stay as they were.

Questions to ask before you choose

  • Which of my providers does the agent read in place today? Ask for the list and for a case that uses them.
  • Can I swap one layer without touching the rest? Ask what changes in the case record when a provider changes.
  • Does the case show where each result came from? Each finding should name its provider and the time of the check.

Cogentic handles

  • Reading your analytics, identity, screening, custody and case systems in place
  • Supplying customer verification, monitoring, sanctions screening or wallet intelligence for layers you choose
  • Applying your SOPs to every case and recording the sources

Your team still owns

  • Choosing which layers to keep and which to change
  • Owning the provider contracts you keep
  • Reviewing each case and deciding the outcome

Frequently asked questions

Do we have to replace Chainalysis, TRM, Elliptic, Sumsub or ComplyAdvantage to use Cogentic?

No. Cogentic reads those providers in place and each finding keeps the provider it came from.

Can Cogentic provide the KYC, monitoring, sanctions and wallet layers itself?

Yes. Cogentic supplies customer verification, transaction monitoring, sanctions screening and wallet intelligence. You choose per capability and can change one at a time.

Does the investigation change if we switch a provider?

No. The result, its source and the time of the check land in the same case whichever provider supplied them.

How do alerts and customers reach Cogentic from our systems?

Through the REST API, with webhooks keeping your systems in step as cases move.

Is the agent able to file a report on its own?

No. The agent drafts. Your team reviews, edits and submits through its own filing process.

Written by

Cogentic Team · Compliance Team

Related articles

View all insights
Design partner

Build the compliance stack for onchain finance.

Become a design partner