[Support]
FAQ
Straight answers to the questions that come up most.
Questions
What does Knovo actually check?+
Knovo pulls live liquidity, market, and trading data from Dexscreener, plus on-chain holder distribution from Moralis where supported, and combines them into a single 0-100 risk score with an AI-written explanation.
Which chains are supported?+
Market data covers any chain indexed by Dexscreener. Deeper holder-distribution analysis currently covers Ethereum, Base, BNB Chain, Polygon, Arbitrum, Avalanche, and Solana.
Is a Knovo score financial advice?+
No. It's a research aid built from public on-chain and market data. Always do your own research before trading.
Do I need an account or API key to use it?+
No signup or API key is required to use the hosted app or call POST /api/analyze. Paste a contract address and run a scan.
How is the risk score calculated?+
The score blends liquidity depth, market cap, holder concentration, trading activity, buy/sell pressure, price volatility, and pool age into one 0-100 read, using a fixed set of rules. See Risk Score Methodology for the exact breakdown.
Does the AI decide the score?+
No. The score is computed by deterministic arithmetic, not a language model. The AI summary only explains a score that has already been calculated, and it's explicitly instructed not to change it.
Do you store the addresses I search?+
No. Knovo doesn't use a database; each scan is processed and returned without being saved.
Why is holderDistribution sometimes null?+
Holder data depends on Moralis. If the token is on an unsupported chain, MORALIS_API_KEY isn't configured, or the lookup fails, Knovo returns the rest of the scan normally and simply omits holder data.
What are the launchIntelligence and riskVerdict fields for?+
They're reserved fields for upcoming launch-forensics and short-label verdict features that aren't wired into the live scan yet. launchIntelligence is currently always null, and riskVerdict is always an empty string.
Is there rate limiting?+
Knovo itself doesn't enforce rate limiting or require an API key on /api/analyze. If you're integrating it programmatically at volume, add your own client-side throttling.
Didn't find your question? See How It Works or the API Reference, or run a scan directly with /api/analyze.