> 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/authentication/how-keys-work.md). # How Keys Work What a serial key is, and what it gives you. Every script you buy is unlocked by a **serial key**. ## Key basics * **One key per script.** Keys are product-specific — an Operation One key does not unlock Phantom Forces, and vice versa. * **Keyed to a plan.** Keys carry the plan you picked at checkout. Plans run on a time limit (for example day-based plans) or are lifetime. * **One device at a time.** A key binds to a single hardware ID once activated. See [HWID Binding](/authentication/hwid-binding.md). * **Redeemable once.** Keys are meant for one buyer. Redeeming a key (for example through a Discord panel) links it to you; it cannot be transferred afterward. ## What your key does not do * It does not unlock every device you own at once. * It does not carry between different scripts. ## Checking your key Your active keys and remaining time are visible on your dashboard and in the Discord buyer panel (**Get Stats**). --- # 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/authentication/how-keys-work.md?ask=&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.