Chainy
Risk
Desk.
Wallet screening, deposit review, tracing, and reports in one place.
One workspace. Four flows.
Wallet, deposit, batch, and transaction review.
Built like a product.
Direct sanctions links and mixer adjacency detected.
Screening with evidence.
Risk score, category weights, and report-ready context in one view.
Queue deposit decisions.
Review incoming deposits with route context and a clear next action.
Graph the case.
See counterparties, entity labels, and escalation paths in one map.
curl --request POST https://app.chainysoft.io/api/external/checks/create \
--header 'X-API-Key: live_x7c9...' \
--header 'Content-Type: application/json' \
--data '{"address":"0x4c8e...f31","network":"eth","report":"html"}'
Operate by API.
Run checks, fetch reports, and manage the workspace from one admin surface.
Readable risk.
Show what triggered the score.
- Risk score with thresholds.
- Direct and indirect exposure.
- Clear network context.
Deposit review.
Wallet, deposit, batch, and tx checks in one flow.
- Allow, review, or block.
- Keep checks in one queue.
- Shorten manual review.
Graph workspace.
See the path, context, and escalation route.
- Entity clusters and risk routes.
- Saved case state and analyst notes.
- Decision context ready for handoff.
API-first operations.
Docs, keys, billing, and transfer tools already exist in the product.
curl -X POST https://app.chainysoft.io/api/external/checks/create \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"address": "0x4c8e...f31",
"network": "eth",
"report": "html"
}'
{
"check_id": "chk_1042",
"risk_score": 78.3,
"status": "queued",
"report_url": "/reports/chk_1042.html"
}
Straight answers.
What does the Chainy risk score represent?
Chainy uses a 0-100 score. Low means cleaner history. High means direct or meaningful indirect exposure.
Which public workflows are already available?
Wallet checks, deposit checks, batch checks, tx checks, USDT tracing, API keys, billing, and referrals.
Can Chainy be integrated into an external product?
Yes. External API routes already cover wallet checks, deposits, USDT transfers, and balance.
Which networks should the landing mention today?
Public flows mention ETH, BSC, TRX, BTC, and LTC. Deposits and USDT tracing use supported subsets.
Does the redesign change the existing payment and report flow?
No. The flow stays the same: address, email, payment, report.
Sharper front end. Same flow.
Better presentation without changing the current backend path.