Exact-chain matching matters
A token address or symbol on another chain must not improve the Base risk picture. The relevant context is the exact token contract on Base and its matching Base market.
Jepeta deliberately rejects cross-token and cross-chain substitutions in its risk model. It uses DEX Screener market context only when it matches the requested Base contract.
How Jepeta exposes liquidity
The V4 compatibility contract exposes liquidity_usd; historical evidence pages publish the matching Base market observation at checks.liquidity.usd in their JSON. V5 represents market context in normalized evidence. Source status separately identifies usable, partial, rate-limited or unavailable provider data.
This separation matters because evidence completeness is not the same thing as risk. Missing data can lower confidence without proving that a token has no liquidity.
Use liquidity with other signals
Liquidity does not tell you whether a contract can mint, block transfers, or impose taxes. Conversely, a clean contract signal does not solve shallow market depth.
Read liquidity together with holder concentration, taxes, mintability, and the timestamp. Market conditions can change quickly.
Separate a market snapshot from an executable quote
Two pools can contain the same Base token but use different quote assets, fee tiers or liquidity designs. Keep pool identity when comparing observations. A displayed USD liquidity value alone does not calculate the slippage of your intended order: that needs the relevant route, trade size and current executable quote. Comparing different pools at different times cannot, by itself, establish that one pool lost liquidity. This is a review method, not a measurement of execution quality.
AI-assisted review of linked documentation; no independent product benchmark. Screening observations and policy labels do not guarantee token safety.
Practical checklist
- Match exact token and Base chain
- Use USD liquidity as market context
- Read source status
- Do not map missing data to zero
- Combine with holder and permission risk
Limitations
Sources & methodology
Sources reviewed Nov 4, 2026.



