> For the complete documentation index, see [llms.txt](https://zenko.gitbook.io/zenko-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zenko.gitbook.io/zenko-whitepaper/institutional-grade-products/token-analyzer.md).

# Token Analyzer

Zenko’s Token Analyzer is a real-time, AI-augmented analytics platform designed to surface actionable intelligence across thousands of digital assets. It enables traders, analysts, and automated systems to identify opportunities, assess risks, and monitor performance using structured on-chain data, machine learning models, and customizable dashboards.

This product suite is tightly integrated with the Zenko Exchange and strategy engine, allowing users to convert insights into trade execution or automated responses without leaving the platform.

#### Core Capabilities

**1. Token Scanning Engine**

* Monitors thousands of tokens across supported chains in real time
* Filters by price action, volatility breakout, volume surge, and trend strength
* Scoring system based on liquidity, order book depth, market cap velocity, and historical ROI
* Configurable alerts for new token listings, rapid inflows, or suspicious spikes

**2. On-Chain Analytics**

* Wallet activity analysis (top holder concentration, token unlock schedules, smart money movement)
* Contract audit summary integration and exploit scoring
* Real-time DEX pool monitoring for slippage risk, MEV vulnerability, and wash trading behavior
* Liquidity pool health metrics (depth, age, lock ratio, pool ownership)

**3. Sentiment and Behavioral Analytics**

* AI-curated sentiment scores based on social media, Discord, Twitter, and Telegram scraping
* Real-time NLP tagging (e.g., bullish/bearish intent, fear index, whale chatter)
* Signal weighting based on source credibility and time-decay functions
* Heatmaps showing directional retail vs. institutional sentiment divergence

**4. Risk Intelligence Module**

* Token risk profiling: volatility, rug probability, insider trading indicators
* Whale activity tracker: large wallets entering/exiting a position, clustering analysis
* Smart contract anomaly detection (e.g., admin access, mint functions, liquidity freeze switches)
* DeFi risk scoring across lending, swaps, and farming protocols

**5. Portfolio Insights & Strategy Overlay**

* Real-time PnL breakdown across connected wallets or API keys
* Attribution analysis (which assets, strategies, or decisions drove returns)
* Backtest integration with bot execution layer: “scan-to-trade” workflow
* Custom risk profiles (e.g., max exposure to unaudited tokens, blacklist triggers)

***

#### Integration and Access

* **User Interface:** Available as a dashboard inside the Zenko platform
* **API Access:** REST and WebSocket APIs for real-time strategy feeds and bot integration
* **Webhook Triggers:** Alerts can auto-trigger bot actions, risk offloading, or portfolio rebalancing
* **SDK Modules:** Available in Python and JavaScript for programmatic traders and data scientists


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zenko.gitbook.io/zenko-whitepaper/institutional-grade-products/token-analyzer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.