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

# Power-ups

Power-ups are boosts you fire during a song.

| Power-up      | What it does                                              |
| ------------- | --------------------------------------------------------- |
| Streak shield | Keeps your streak alive through misses for a few seconds. |
| Beat burst    | Gives you 10 seconds of 16x.                              |
| Hype start    | Starts the song at a higher multiplier.                   |

## How they work

* You take up to 2 power-ups into each song.
* Beat Burst and Streak Shield each have their own button, away from the lanes. Fire them between taps.
* Hype Start has no button. It fires by itself when the song starts.
* A power-up is used up only when it fires. Unused ones stay yours.
* Power-ups in your wallet work too. A fired one is burned, so a used power-up can't be sold.
* Moved a power-up out of your wallet and back? Tap **Enable in game** to play it again. You pay the small network fee.
* Power-ups count toward your score and your crowns.

## Getting them

Runs drop power-ups. You can trade them with other players.


---

# 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://beatking.gitbook.io/beatking-docs/gear/power-ups.md?ask=<question>&goal=<user_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.