> For the complete documentation index, see [llms.txt](https://docs.bao.la/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bao.la/baola-docs/baola-product-documentation/core-features/k-line-page.md).
# K-line Page
#### **1、Token Basic Information and Market Overview**
The top of the page centrally displays the token's logo, name, associated network, issuing platform, creation time, and contract address, allowing users to easily confirm the asset they are viewing. It also provides access to the current market capitalization, price, 24-hour trading volume, liquidity, and token audit results, helping users quickly grasp the token's scale, trading activity, and basic risk profile.
#### **2、Multi-period K-line Chart**
It offers multiple observation intervals including second-level, minute-level, hour-level and day-level. The current page provides quick options for 1 second, 10 seconds, 30 seconds, 1 minute, 5 minutes, 1 hour and 1 day. Users can observe real-time fluctuations through shorter intervals, review overall trends through longer intervals, and analyze market changes in combination with trading volume. The specific available intervals are subject to the token page.
#### **3、K-line Dot Plot**
It supports overlaying information such as "My Trades", "KOL Buys" and "Trade Calls" on the chart, mapping the positions where trading actions and opinions appear to the price trend. Users can intuitively compare their own entry and exit points, the timing of KOL participation, and price changes before and after trade calls, to assist in reviewing their trading process. Layers can be displayed or hidden as needed.
#### **4、Filter by Tracking Platform Source**
The chart overlay provides source filtering options including FOMO, Pump, GMGN, X, Baola and Other, allowing users to focus on KOL activities and call-to-trade information from specific platforms. Combined with layer type filtering, it reduces information clutter on the chart and enables users to observe the market according to their areas of interest.
#### **5、Token Call Signal Feed**
Aggregates trading call content related to the current token, displaying the publisher, platform source, publication time, main text of the viewpoint, as well as available position and profit/loss information. It supports viewing all content, followed accounts, and featured posts. For foreign-language viewpoints, a toggle between the original text and translation is provided, allowing users to easily understand discussions about the token across different communities and combine these viewpoints with actual position data for research.
#### **6、KOL Trading Dynamics**
It centrally displays the buying and selling dynamics of KOLs on current tokens, helping users understand the participation status and trading directions of different KOLs. Combined with candlestick chart trends and call order content, users can compare KOLs' opinions with their actual trading behaviors, observe their position building, adding or reducing movements, and gain references for market trend judgment and trade review.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bao.la/baola-docs/baola-product-documentation/core-features/k-line-page.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
