> For the complete documentation index, see [llms.txt](https://polyhelper.gitbook.io/polyhelper-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polyhelper.gitbook.io/polyhelper-docs/analytics-tools/mrbeast-intel.md).

# MrBeast Intel

Stop counting views manually every 10 minutes. **MrBeast Intel** tracks YouTube video velocity, performance status, and 24H projections — displayed directly on Polymarket without switching tabs.

Created by traders for traders.

Open it via the **MrBeast** icon in the right-side panel navigation.

![MrBeast Intel Panel](https://raw.githubusercontent.com/polymarkethelper/gitbook/main/.gitbook/assets/mrbeast-intel.png)

***

## What the Panel Shows

### Current Speed & Status

The top of the panel shows the live view velocity with an instant performance read:

* **Views/hr** — current speed in real time (e.g., 538.6K views/hr)
* **Performance status** — how the video is doing vs. its historical baseline:
  * `Overperforming` — ahead of average
  * `On Track` — performing as expected
  * `Underperforming` — below average pace

### Speed Selector

Switch between time windows to see average speed over different periods:

| Tab     | What It Shows                |
| ------- | ---------------------------- |
| **1h**  | Speed over the last 1 hour   |
| **2h**  | Speed over the last 2 hours  |
| **4h**  | Speed over the last 4 hours  |
| **6h**  | Speed over the last 6 hours  |
| **12h** | Speed over the last 12 hours |

### Key Metrics

| Metric             | Description                                                                                  |
| ------------------ | -------------------------------------------------------------------------------------------- |
| **Speed**          | Views per hour for the selected window + total views gained                                  |
| **VS Average**     | Performance multiplier vs. the video's/channel's baseline (e.g., 0.5x = half the usual pace) |
| **Trend**          | Direction of momentum — Steady, Rising, or Falling                                           |
| **24H Projection** | Estimated total views by end of 24 hours based on current pace                               |

### Views Per Hour Bar Chart

Hourly bar chart showing view velocity over time. Reveals when the video peaked and how momentum is shifting.

Time range selector: **6H · 12H · 24H · Full**

### Total Views Line Chart

Cumulative view count curve over time — shows the growth trajectory from upload to now.

Time range selector: **1H · 12H · 24H · 48H · 7D**

***

## Data Refresh Rate

The panel updates every **10 minutes** — giving you fresh data without any manual refreshing.

***

## How to Use It

**For view count milestone markets** (e.g., "Will this video hit 100M views?"):

1. Check the **24H Projection** — if the projection already puts the video past the milestone, the YES is likely underpriced
2. Look at **VS Average** — 0.5x means it's running slow, 2x means it's viral. Calibrate your expectation accordingly
3. Check the **Trend** — a Falling trend means deceleration; the projection may end up lower than shown

**For view range markets** (e.g., "Will this video get 40–60M views in the first week?"):

1. Use the **Total Views** chart to see the current cumulative count and trajectory
2. Compare the pace to past videos from the same creator using the VS Average multiplier

**For upload frequency markets**:

* Active view tracking signals a video is live — useful for "Will \[creator] upload this week?" markets

***

## Markets Where This Panel Activates

* [YouTube view count and milestone markets](https://polymarket.com/pop-culture/mrbeast)
* [# of views of next MrBeast video on day 1?](https://polymarket.com/event/of-views-of-next-mrbeast-video-on-day-1-966)
* Creator upload frequency markets
* Any market involving YouTube content or channels


---

# 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://polyhelper.gitbook.io/polyhelper-docs/analytics-tools/mrbeast-intel.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.