> For the complete documentation index, see [llms.txt](https://docs.getcelsius.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getcelsius.net/getting-started/activating-your-key.md).

# Activating Your Key

Entering your serial key and binding your license.

The first time you run a loader, the script authenticates your **serial key** against our servers. Once it succeeds, the key is **bound to your PC** and the script unlocks.

## First run

1. Make sure you have your serial key from your purchase (email or dashboard).
2. Run the loader in-game with a [supported executor](/getting-started/executor-requirements.md).
3. Enter your serial key when prompted.
4. Wait for the authentication message. Success unlocks the script; failure prints a reason.

## What counts as activation

Activation is tied to your **hardware**, not your account. The first successful run on a PC binds that key to that PC's hardware ID (HWID). From then on, that key works on that PC without re-entering it.

## If authentication fails

The loader prints a `[CELSIUS]` message with the reason. See [Common Errors](/troubleshooting/common-errors.md) for what each message means.


---

# 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://docs.getcelsius.net/getting-started/activating-your-key.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.