> For the complete documentation index, see [llms.txt](https://docs.tachyo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tachyo.ai/platform/feed.md).

# Live Feed

The Feed is the real-time stream: every buy and sell from tracked wallets, with the tier of the wallet behind it. It is the screen to keep open, and the one to filter hardest.

The header marks the feed **LIVE** when the newest event is under five minutes old.

<figure><img src="/files/Dt7O6E2OIWkN3O2YKU7N" alt=""><figcaption></figcaption></figure>

## Two views

**List** shows chronological events, one row per trade:

| Column            | What it is                                             |
| ----------------- | ------------------------------------------------------ |
| **Time**          | When it landed.                                        |
| **User / Wallet** | Who traded, with their tier.                           |
| **Type**          | Buy, sell, or another tracked event kind.              |
| **Token**         | What they traded, with the chain.                      |
| **Amount**        | Size in USD.                                           |
| **Price**         | Execution price.                                       |
| **PnL %**         | Where relevant, the result on the position.            |
| **Swaps**         | How many swaps make up the row when events are merged. |

**By token**: the same flow grouped by token, so you see *how many* scored wallets touched something rather than a stream of individual rows. Each token carries a buy/sell bar and its market cap, and selecting one opens an intelligence panel beside the list without leaving the page.

By token is the better default once you know what you are looking for. List is better when you are watching a specific wallet or a specific hour.

## The 24h strip

Above the feed sits the regime strip: buys against sells over 24 hours, net flow, and how that flow skews by event kind and by chain. It is the aggregate view: one glance tells you whether the day is accumulation or distribution across the whole tracked population.

## AI recap

The recap card is a written summary of the current window: what stood out, where the flow concentrated, which names keep recurring. It carries its generation timestamp, so you always know whether you are reading something fresh or something from earlier.

The strip owns the numbers; the recap owns the interpretation.

## Filtering

The feed is loud by default. The filters that matter most:

* **Tier chips**: the single highest-value filter. S and A only, and the feed becomes readable.
* **Minimum amount**: hide events below a USD value.
* **Minimum market cap**: hide tokens below a market cap. Tokens with unknown market cap are always shown rather than silently dropped.
* **Chain** and **launchpad**.
* **Mute or solo KOLs**: mute the ones you do not want, or solo one to watch only them.
* **Raw feed toggle**: turns off the dust and low-liquidity gates that hide airdrop spam. Useful when you suspect something is being filtered out; noisy otherwise.

{% hint style="info" %}
Volume shown in the feed is **tracked-wallet volume**, not market volume. A token showing nothing here can still be trading actively on the open market. It just is not being touched by wallets we score.
{% endhint %}

## A workable routine

1. Tier filter to S + A, minimum amount set to something meaningful for your size.
2. Switch to **by token** and scan for tokens where several scored wallets appear within a short window.
3. Open the intel panel on anything that repeats, then the full [token page](/platform/token-page.md) if it survives that look.
4. Add the survivors to your [Watchlist](/platform/watchlist.md) instead of trying to hold them in your head.


---

# 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://docs.tachyo.ai/platform/feed.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.