> 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/live-narratives.md).

# Live Narratives

Live Narratives is KK.one's public discovery feed. It connects an original public X post with the narrative detected around it and the independently launched tokens associated with that narrative.

## Browse and search

You can:

* sort by **Newest**, **Most Tokens**, **Top Volume**, or **Max Cap**;
* filter to **All**, **Base**, or **Robinhood Chain**;
* search for narratives, tokens, or X accounts;
* open the original post on X;
* open a Narrative Detail or Token Detail page;
* trade an eligible token on its own network.

A network filter includes narratives that have at least one successfully indexed token on that network. Filtering does not combine or convert tokens across networks.

## Read a narrative card

A card separates the source from its onchain results:

* **Caught on X** shows when the source post was published or detected.
* **First token** shows the time from the source post to the earliest successfully confirmed and indexed token.
* **First on each chain** shows the first successful token for each supported network.
* **More tokens** lists later successful deployments from the same narrative.

`#001` means the first successfully created token for that narrative on that network. Later successful tokens on the same network use `#000`; KK.one does not use `#002`, `#003`, and so on.

Pending, failed, reverted, or unindexed attempts are not counted as successful tokens and do not receive a first-token position.

## Source and endorsement

The source post provides narrative context. It does **not** mean the source author created, approved, sponsored, or recommends any token. If a source becomes unavailable on X, KK.one may retain a lawful cached reference and mark the source unavailable rather than erase valid onchain history.

## Data states

KK.one distinguishes these states:

* **Syncing / Loading** — the request has not finished.
* **0 / No token yet / No trades yet** — the request succeeded and the value is truly zero or empty.
* **Unavailable** — the service could not provide the value.
* **Confirmed · Market data syncing** — the chain transaction is confirmed but downstream indexing is not complete.

Market values are estimates from external data sources. Different networks are never added together as if they were one tradable pool.


---

# 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/live-narratives.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.