API
USDT checks inside your system.
For exchangers, OTC desks and P2P teams. Send a TRON address or a transaction hash and get the 🟢 / 🟡 / 🔴 verdict with reasons as JSON. It is the same engine as @freezecheck_bot.
Try it in a minute, no code. In the API console you get a trial key at once (100 checks a day for 20 days), paste a list of addresses or upload a CSV, and download the result for Excel. Copy-paste code for Python, PHP and Node.js is there too. For a bigger limit, write to hello@freezecheck.org or Telegram @freezecheck_support.
Request
One endpoint, a GET request. Put the key in a header, not in the URL.
curl -H "Authorization: Bearer fc_xxxxxxxx_…" \
"https://freezecheck.org/api/v1/check?address=TXyz…&lang=en"
| Parameter | What it is |
|---|---|
address | TRON address (T…), the wallet to check. |
tx | Instead of an address: a transaction hash. We check the sender of the largest USDT transfer in it. |
lang | Language of the texts: en (default), ru, es, pt, tr, ar, id, uk, vi, zh. |
The key header can also be X-API-Key: fc_….
Response
{
"address": "TXyz…",
"chain": "tron",
"verdict": "yellow",
"action": "review",
"score": 46,
"confidence": "high",
"title": "Some questions",
"signals": [
{"code": "taint_dirty", "severity": "high", "points": 25,
"text": "2 hops from a wallet frozen by Tether: 1,200 USDT"},
{"code": "mature", "severity": "positive", "points": -5,
"text": "Wallet has been active for 2 years"}
],
"checked_at": "2026-11-18T09:15:02+00:00",
"cached": false,
"report_url": "https://t.me/freezecheck_bot?start=w_TXyz…",
"usage": {"today": 128, "daily_limit": 1000}
}
| Field | What it means |
|---|---|
verdict | green: no risk found. yellow: caution, read the reasons. red: high risk. unknown: not enough data. |
action | What your code should do, in one word: accept (green), review (yellow or unknown: show to a manager with the reasons), hold (red: do not credit, hold the funds). |
score | Risk score from 0 to 100. |
confidence | high / medium / low: how complete the analysis was. |
signals | Reasons, most important first. code is stable and safe to match in your code; severity is critical, high, medium, low or positive; points is the share in the score. |
checked_at | When the blockchain data was read. |
cached | true: the answer came from a recent check of the same address. |
report_url | The full report with the link graph and PDF in the bot. |
tx | Only for tx=: id, from, to, amount, at of the transfer. |
usage | Checks used today and the daily limit of the key. |
Batch: up to 50 addresses in one call
Useful for payouts: split a batch into “pay now” and “hold for review” in one pass.
curl -X POST -H "Authorization: Bearer fc_xxxxxxxx_…" \
-H "Content-Type: application/json" \
-d '{"addresses": ["TXyz…", "TAbc…"], "lang": "en"}' \
https://freezecheck.org/api/v1/batch
The answer has results in the same order as you sent the addresses. Each item has the same fields as a single check, or an error for that address (bad_address, quota, slow, source_down). There are also checked and usage. Each address with a verdict counts once toward the daily limit. A batch of new addresses can take a few minutes, so set your client timeout to 10 minutes.
Limits and timing
Each key has a daily limit, and it resets at 00:00 UTC. Every answer with a verdict counts, including answers from cache. Errors don't count.
A new check usually takes 5–15 seconds, and a very large wallet can take up to two minutes. Set your client timeout to 180 seconds. A repeat check of the same address within the cache window answers at once.
Usage so far: GET /api/v1/usage with the same header returns today, daily_limit and resets_at.
Errors
| HTTP | error | What to do |
|---|---|---|
| 400 | bad_address | Pass a TRON address or a 64-character transaction hash. |
| 400 | bad_batch | Batch only: send JSON {"addresses": [...]} with 1 to 50 addresses. |
| 401 | no_key, bad_key | Add the header; check the key was not revoked. |
| 403 | trial_over | The 20-day trial has ended: write to hello@freezecheck.org or Telegram @freezecheck_support to keep access. |
| 404 | tx_not_found | There is no USDT (TRC-20) transfer in this transaction. |
| 429 | quota | The daily limit is used up; see resets_at. |
| 429 | busy | Too many new checks at once for this key: retry in a few seconds. |
| 503 | slow, source_down | Retry in a minute. |
Every error has a message in plain English.
How to use the verdict
A common setup is exactly the action field: accept green automatically, send yellow to a manager with the reasons, and hold red. How the score is built is described in the methodology. The verdict is a heuristic estimate, not a legal AML opinion.