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

# Narrative and Token Detail

## Narrative Detail

Narrative Detail is the evidence page for one detected narrative. It preserves the connection between the original X post, the first successful token on each supported network, and all successfully indexed tokens associated with the narrative.

The page includes:

* original X account, post text, media, source time, and source link;
* a narrative summary and snapshot;
* first successful token on Base and Robinhood Chain;
* the full successful token list, ordered by confirmed onchain time;
* network, contract, launch time, and market information where available.

The first-token section and the full list may both show the same `#001` token. That is intentional: one section highlights firsts, while the other is the complete history.

## Token Detail

Token Detail is the canonical page for one **network + contract address**. A name, ticker, image, or narrative is not a unique token identity.

![Token Detail design reference](https://3432547454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGNEktUyRlEG9fdq2CvXW%2Fuploads%2Fgit-blob-7854f09a651ccc3f2c4d8e35548ccea624d62050%2Ftoken-detail.png?alt=media)

*Illustrative demo. Token names, addresses, balances, prices, market data, fees, protocol labels, and dates in screenshots are not production constants.*

The page may include:

* origin narrative and source X reference;
* network, contract address, deployment time, and explorer link;
* price, market cap, liquidity, volume, holders, chart, and trades;
* Buy and Sell actions where trading is available;
* the current Trading Wallet and network;
* Creator Tools for the verified creator;
* creator allocation, current creator holding, and claimable rewards.

## Creator allocation versus current holding

For current Base and Robinhood Chain launches, the creator allocation is **2% of total token supply at launch**. Creator Holding is the creator wallet's current balance as a percentage of supply and can change after transfers or sales. It is not a restatement of the initial 2% allocation.

Creator Allocation and Creator Rewards are also different:

* **Creator Allocation** is the token amount allocated at launch.
* **Creator Rewards** are network-specific amounts that may become claimable under the applicable onchain configuration.

## Trading and creator identity are separate

The Trading Wallet used to Buy or Sell can be an in-product wallet or a supported connected external wallet. Changing it does not change the signed-in creator account, creator ownership, or the wallet to which creator rewards are assigned.

Creator Tools require server-side creator verification. Connecting an external wallet alone does not grant creator access.

## Links and addresses

Always verify the network and complete contract address before trading or sending assets. Explorer links, transaction hashes, and market data are network-specific. A Base contract and a Robinhood Chain contract with the same name or ticker are separate assets.


---

# 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://kkone.gitbook.io/kkone-docs/discover/narrative-and-token-detail.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.