> For the complete documentation index, see [llms.txt](https://docs.luasec.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luasec.org/licensing/keys.md).

# Keys & the key system

A **key** authorizes an end user to run your scripts. Keys belong to a **project**, so one key works for every script in that hub.

<figure><img src="/files/cpolZduUtuIqA15AQS55" alt=""><figcaption></figcaption></figure>

## Minting keys

From your project's **Keys** page:

* **Count:** mint one or many at once.
* **Expiry:** optional; leave empty for a never-expiring key.
* **Note:** free text, surfaced to your script as `SEC_Note` and shown in webhook logs.
* **Discord ID:** link the key to a Discord user; surfaced as `SEC_DiscordID`.
* **Premium:** sets `SEC_IsPremium` for freemium gating.

The raw key value is shown **once** at mint time. Store it then — the server only keeps a hash and an encrypted copy for re-display.

## Key states

| Status     | Effect                                                                    |
| ---------- | ------------------------------------------------------------------------- |
| **active** | Works normally.                                                           |
| **paused** | Temporarily rejected at the handshake (`key_paused`). Unpause to restore. |
| **banned** | Rejected permanently (`key_banned`).                                      |

Expiry is enforced on every run. An expired key is rejected with `key_expired`.

## HWID locking

The first device to use a key **binds** its HWID. After that, the same key on another device is rejected (`hwid_mismatch`). This turns "one leaked key" into "one device", which is trackable and bannable. See [HWID locking & resets](/licensing/hwid.md).

## Executions & activity

Each run increments the key's execution count (`SEC_ExecutionCount`) and refreshes its last seen time. These roll up into your [analytics](/account/analytics.md).

## Ways to hand out keys

* **Manually:** mint and DM/sell the raw key.
* **Discord bot**: whitelist a buyer and the bot manages their key + buyer role. See [Discord bot](/discord-bot/setup.md).
* **Ad rewards**: users earn a temporary key by passing ad checkpoints. See [Ad rewards](/licensing/ad-rewards.md).


---

# 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.luasec.org/licensing/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.