> For the complete documentation index, see [llms.txt](https://docs.riku.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riku.ai/fundamentals-of-riku/connecting-keys/connecting-muse-api-keys.md).

# Connecting Muse API Keys

First of all you will need to sign up for a plan at <https://muse.lighton.ai/home>. You will be required to enter card details for this but the free plan is extremely generous. You can see our first look on the pricing and website here - <https://www.youtube.com/watch?v=cbhipy5URaM>.

Once your account is created and you are logged in on the Muse site, you will see "Account" in the top right. Click on this and choose the option for "API Keys".&#x20;

![Create a new key and name it Riku. It is that simple!](/files/eOuo5qBmRQcVJ3rOinCw)

From here, you can hit "Add key" in the top right and you will be able to give your new key a name. Call it Riku or whatever you want and you will then be able to copy it to the clipboard. From here, go back to the Riku Dashboard and the API Settings and enter it in the Muse API box and hit save. Your connection will now go green and Muse is ready to use within Riku!


---

# 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.riku.ai/fundamentals-of-riku/connecting-keys/connecting-muse-api-keys.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.