Discovery is not evidence history
A feed is optimized for recency: token, decision, scores, timestamp, and source platform. It helps an agent or researcher notice what Jepeta has published recently.
A permanent evidence page is optimized for verification: it freezes the public snapshot, methodology link, timestamps, and raw evidence dimensions at a canonical URL.
Agent workflow
Poll the risk feed with bounded frequency, deduplicate by publication and token, then follow the token to a fresh scan or evidence page when deeper context is needed.
Do not treat feed absence as evidence that a token is safe. The feed contains published discovery signals only and is not a census of Base tokens or all Jepeta scans.
Human workflow
The public Risk Monitor and evidence catalog provide a browsable view without requiring a wallet. Telegram and Farcaster distribution can surface selected signals, while the canonical evidence URL stays on jepeta.dev.
For execution, use a fresh scan because a feed item or evidence page can be older than the intended trade.
Practical checklist
- Feed for recency
- Evidence page for durable reference
- Fresh scan for current execution
- Do not infer safety from absence
- Respect rate limits