Use casesFinancial institutions & fintech
Every crypto transfer a provider sends or receives must carry who sent it and who receives it; incomplete messages, wallets no provider holds, and foreign counterparties each wait for a compliance analyst.
With the systemEach message checked, each gap tracked through your policy's steps, each counterparty read; the analyst decides.
Travel-rule message · incoming · 4 November 2026
Originator information · transfer message
Originator: S*** T***. Wallet address: 0x7f3…a91c. Identifier: not provided (no address, birth date, or ID number).
→ above the threshold: one identifier required
The analyst gets the message already checked by your own rules, the gap tracked through your policy's steps with every move timed, and the counterparty and its reply read with sources. Releasing or returning the transfer stays the analyst's; a provider that keeps sending gaps goes to the compliance officer.
Code · message checks
Agent · states and moves
SLM · counterparty and reply
Status
Why a person decidesReleasing, returning, or holding the transfer is the compliance analyst's; a counterparty relationship and any report are the compliance officer's.
DecidesCompliance analyst
For your technical team — skip it if you like.
In
Code · calculates
Your written rules and threshold table, run as code; no model
Reads
Out
Agent · acts
State graph; each transfer moves only along your policy's steps
Reads
Out
SLM · reasons
Fine-tuned SLM; reads provider documents, declarations, and replies
Reads
Out
Decision
Reads
Out
State graph
Each transfer sits in one named state (complete, information requested, completed, to return, declaration pending, held for review), and your policy writes which moves each state allows and how long each may wait, so the agent cannot invent a step.
Your expert writes the test first. A step the test does not need is skipped, and we say why.
Test set
200–400 past transfers with your analysts' review notes, counterparty reviews, and declarations, graded by your senior compliance staff before any training.
Dataset
Past messages, requests and replies, counterparty due-diligence files, and customer declarations; personal data masked in training copies where the test allows.
Continued pre-training (CPT)If needed
Only if the base model fails the test on crypto-asset and anti-money-laundering vocabulary in Turkish and English.
Supervised fine-tuning (SFT)
On reading counterparty licenses, AML questionnaires, declarations, and replies, and on your review note template.
Reinforcement learning (RL)Skipped
Skipped: reading documents and writing to a template are taught by fine-tuning, and the field checks are code.
Retrieval
Your counterparty register, your policy, and the regulation's text are retrieved at each review; the threshold is set by regulation and changes, so it lives in the code's table, never in the model's weights.
Monitoring
The analyst corrects every note; a missed gap or a wrong reading joins the next test.
Under your policy, the compliance analyst releases, returns, or keeps holding each transfer; the compliance officer decides whether to limit or end a relationship with a provider that keeps sending incomplete messages, and on any suspicious transaction report.
Where the time goes, and what your institution will measure.
Measured in the Decision Blueprint
Analyst minutes per held transfer and the time a held transfer waits, from your platform's log, set the baseline; your institution sets the target.
The rules, the data, and the known error, with its guard.
We take a month of held and incomplete transfers with your compliance team, time each follow-up, map your policy's states and waits, and test the reader on your own counterparty files and declarations before anything is built.
Who builds it Every engagement is led by an engineer who has built machine-learning models that real decisions run on since 2012, and language models and agentic systems in production since 2024. About eqlx
Equalize the gap.
A short description of the work is enough; no confidential records.
https://eqlx.ai/use-cases/crypto-travel-rule · Printed copy; the website is the current version.