> For the complete documentation index, see [llms.txt](https://xemlok.gitbook.io/xemlok-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xemlok.gitbook.io/xemlok-docs/how-token-analysis-works.md).

# How Token Analysis Works

{% stepper %}
{% step %}

### Data Collection

Xemlok extracts several kinds of data:

#### A. Technical Chart Data

* recent candle highs and lows
* volatility spikes
* sudden upward or downward pressure

#### B. Liquidity-Related Data

* liquidity amount
* liquidity direction
* liquidity injections or drain

#### C. Token Metadata

* symbol
* contract
* decimals

#### D. Context

Page type, token state, timeframe.
{% endstep %}

{% step %}

### AI Processing

The extension creates a structured prompt describing:

* volatility
* chart behavior
* liquidity
* anomalies
* sudden movements
  {% endstep %}

{% step %}

### Output Generation

AI returns:

* risk level
* summary
* detailed findings
* recommendations
  {% endstep %}
  {% endstepper %}


---

# 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://xemlok.gitbook.io/xemlok-docs/how-token-analysis-works.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.