> 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/development/reference-clients.md).

# Reference clients and migration

## Roblox: use the loader

The old manual Lua reference client and crypto core are retired:

| Route                                      | Current result                        |
| ------------------------------------------ | ------------------------------------- |
| GET /client/vampauth.lua                   | 410 Gone                              |
| GET /client/vampauth-core.lua              | 410 Gone                              |
| POST /api/v1/key/activate                  | 410 with error GONE                   |
| Old project raw/loadstring delivery routes | Retired; use the dashboard loader URL |

Copy the current loader snippet from the dashboard and remove the old manual SDK initialization. Don't ship the project auth secret to players. The loader handles initial validation, payload delivery, and its runtime context.

## Another language: use a backend client

The standalone key-check guide includes a Node.js client that signs requests and verifies the response. It is separate from the retired Lua SDK.

## Management examples

The management recipes include cURL and Node.js examples. A small Python example is below. Set only the environment values needed by the action. Retain the exact original request context when retrying an uncertain mutation.

### cURL

```bash
curl --fail-with-body "$VAMPAUTH_BASE_URL/me"   -H "Authorization: Bearer $VAMPAUTH_TOKEN"
```

### Python 3

```python
import json
import os
import urllib.request

base = os.environ.get("VAMPAUTH_BASE_URL", "https://vampauth.com/api/v2")
request = urllib.request.Request(
    base.rstrip("/") + "/me",
    headers={"Authorization": "Bearer " + os.environ["VAMPAUTH_TOKEN"]},
)
with urllib.request.urlopen(request, timeout=15) as response:
    result = json.load(response)
    print("Account request succeeded:", response.status)
```

These management calls inspect resources without activating a key. A successful standalone key check does activate first-use stock.

## Next steps

* [Loader](/vampauth-docs/development/loader.md)
* [Node.js key-check client](/vampauth-docs/development/key-check.md)
* [Management API recipes](/vampauth-docs/development/management-recipes.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/development/reference-clients.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.