A risk badge for any token project, in one line of HTML. It reports what the checker actually found — a count of red flags and a separate count of signals it could not read. No stars, no approval queue, no paid tier.
Why there are no stars. The checker returns a count of red flags and a count of unreadable signals, because a single number would imply precision this data cannot support. An unreadable signal is never counted as clean, and the badge shows it separately. A "4/5 stars" badge would be a lie in a few kilobytes of SVG.
Independence. No paid promotion. Any project can embed this, whether it passed or failed.
Paste any mint below to preview it, or use the code.
<img src="https://coincheck.clientelai.com/badge/YOUR_MINT.svg"
alt="CoinCheck risk check"
width="260" height="20">
Link the badge so the reader can act on it — that is the point of a badge:
<a href="https://coincheck.clientelai.com/?q=YOUR_MINT" target="_blank" rel="noopener">
<img src="https://coincheck.clientelai.com/badge/YOUR_MINT.svg"
alt="CoinCheck risk check" width="260" height="20">
</a>
GET https://coincheck.clientelai.com/badge/YOUR_MINT.json
Same counts, CORS-open, so a frontend can render
whatever it likes. Fields: red_flags, unreadable,
clean, signals_checked, plus
facts.topWalletShare and facts.poolShare.
| Badge | Means |
|---|---|
| no red flags | Every readable signal came back negative, and nothing was unreadable. That is not a safety endorsement — see the methodology. |
| N could not read | No red flags, but N signals could not be answered. Shown separately precisely so it is never read as a pass. |
| N red flags | N signals came back present — live authorities, concentration, or the others listed in the methodology. |
| not checked | The token could not be read right now. The badge will update on its own. |
It is not a live trading signal. A badge refreshes every 10 minutes. For a decision made in the next ten minutes, run a live check.
A clean badge is not a safe token. The commonest way a memecoin loses money is everyone selling at once, and that is not visible on-chain. The methodology page says this in full.
Cross-chain wallet clustering is not built. That is the largest known gap and the badge cannot see past it.