> For the complete documentation index, see [llms.txt](https://docs.bluedev.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluedev.xyz/premade-bots/music-bot.md).

# Music Bot

## Requirements

### Google API key

A Google API key is required for the searching of videos (-music play \<query>) and for YouTube playlist support (-music play \<Link to a YouTube playlist>).

Information on how to generate one is located [Here](https://developers.google.com/youtube/registering_an_application) (API key)

### Genius API access token

A Genius API access token is needed for the bot to retrieve the lyrics of songs (-music lyrics \[song name).

You may find information on how to generate this token [Here ](https://docs.genius.com/#/getting-started-h1)(Access token)

![](/files/-M9Rx3ZBzNrLlv9ULWii)

## Lyrics

In order to use the lyrics command, you'll need to create a Genius API access token. Instructions can be found above.

To get lyrics for a song, run -music lyrics \[song name]. If the song name isn't specified, the bot will attempt to get the lyrics for the currently playing song.


---

# 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.bluedev.xyz/premade-bots/music-bot.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.
