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

# Getting and using a key

Open the key-page link supplied by the script developer. Choose an available provider and package, complete its checkpoints, and copy the issued key.

Keep the same browser session while completing the flow. A completion link from another browser or an old tab may not belong to your current attempt.

Paste the key into the snippet the developer gave you:

```lua
script_key="PASTE-YOUR-KEY-HERE";
loadstring(game:HttpGet("https://vampauth.com/v1/loaders/YOUR-LOADER-HASH.lua"))()
```

Use the real loader URL from the developer. The placeholder above is not a working loader.

## If the key stops working

* **Expired:** get a new key or use the renewal option when offered.
* **Different hardware:** ask the developer to reset the binding, or use the panel's reset action when permitted.
* **Revoked or blocked:** contact the developer. Repeating checkpoints does not remove a hardware ban.
* **Session limit:** close an older run and wait for its session to end.

The script developer controls durations, bans, reset limits, and packages. Vampauth support can help with platform issues; it cannot promise access to someone else's project.

## Next steps

* [Loader errors](/vampauth-docs/troubleshooting/loader-errors.md)
* [Member actions and commands](/vampauth-docs/integrations/discord/member-actions.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vampauth.gitbook.io/vampauth-docs/getting-started/using-a-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.