Billing
Top up balance, review checks, and run API operations from one control desk.
My Orders
New OrderYour recent orders
| # | Status | Link | Address | Network | Date Created |
|---|
Billing
Current Balance
$0.00
Available funds
Price per Check
$20.00
Cost per verification
Available Checks
0
Based on current balance
Top Up Balance
Select Payment Method
Transaction History
| Date | Type | Description | Amount | Status | Balance After | Actions |
|---|
API Keys
API Documentation Available
Learn how to integrate Chainy API into your application with our comprehensive documentation. Find code examples, authentication guides, and endpoint references.
View API DocumentationCreate New API Key
Your API Keys
| Name | Key | Created | Last Used | Status | Actions |
|---|
Risk Models
Use one model as the default, then override it only where needed.
Risk models do not replace Chainy data. They change how provider data is scored, transformed into a decision, and attached to a specific API key or check type.
Recommended setup flow
- Start from Templates. Clone a template if you want a safe starting point, or create a blank draft only if you already know the full rules structure.
- Edit metadata first: name, code, description. This makes the model readable before you touch scoring.
- Update Rules JSON. Thresholds control hold / reject limits. Category rules control exposure weights. Level rules map provider risk levels to base scores. Meta rules control how the final score is blended.
- Click Save Rules, then use Simulation to verify the output before routing live traffic into the model.
- Add a binding. Bind by API key when one integration needs a custom model. Bind by check type when you want a default model for all wallet checks or all deposit checks.
- Click Activate. Activation publishes the model version, but the model affects live traffic only where it is actually bound.
What each panel means
- Current Applied Model shows which model is currently selected for the chosen API key and check type.
- Your Models are your editable drafts and active versions.
- Templates are starting points. They are meant to be cloned, not edited directly.
- Model Editor is where you change metadata, rules JSON, bindings, and run simulations.
Safe rollout strategy
- Create or clone a draft and keep it unbound while editing.
- Bind it to one test API key first. This is the safest way to validate a model without changing every client.
- Use check type binding only when you want a broad default, for example “all deposit checks use this model unless an API key has its own override”.
- Keep wallet and deposit models separate on purpose. Wallet models affect address checks. Deposit models affect KYT / transaction deposit decisions.
Current Applied Model
Your Models
Templates
Model Editor
Bindings
| Scope Type | Scope Value | Priority | Mode | Status | Actions |
|---|
Referrals
Referral Links
0
Active and archived links
Referred Users
0
Users attached to your links
Rewards Earned
$0.00
Credited to your balance
Referred Revenue
$0.00
Revenue generated by referrals
Create Referral Link
Your Links
| Name | Link | Commission | Referrals | Rewards | Status | Actions |
|---|
Recent Referral Rewards
| Date | Referred User | Source Amount | Reward | Status |
|---|
USDT Transfers
Check USDT Transfers
Total Transfers
0
Total Sent
0 USDT
Total Received
0 USDT
Net Balance
0 USDT
Transfer History
Loading USDT transfers...
| Date | Type | From | To | Amount (USDT) | Transaction Hash |
|---|
Deposit Checks
address,network — supported networks: ETH,
BSC, TRX, BTC, SOL. Max 50 addresses.
Transaction Check Result
KYT Status:
—Decision:
—Risk Score:
—Deposit Checks History Auto-refreshing
| ID | Date | Network | Tx Hash | Address | KYT Status | Risk | Decision | Actions |
|---|
Manual Checks History
| ID | Date | Check Type | Target / Name | Network | Status | Actions |
|---|
Deposit Check Details
Tx Hash:
Address:
Decision:
Risk Score: