> 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/environment-variables.md).

# Environment variables

These are configuration names used by the client examples. They aren't values that Vampauth automatically injects into your operating system.

## Management API clients

| Variable                   | Use                                                                                 |
| -------------------------- | ----------------------------------------------------------------------------------- |
| `VAMPAUTH_BASE_URL`        | API base; normally <https://vampauth.com/api/v2>                                    |
| `VAMPAUTH_TOKEN`           | Scoped management bearer token                                                      |
| `VAMPAUTH_PROJECT_ID`      | Project **UUID** for v2 paths                                                       |
| `VAMPAUTH_KEY_ID`          | Key UUID for management actions                                                     |
| `VAMPAUTH_KEY`             | Plaintext key for exact lookup                                                      |
| `VAMPAUTH_LOADER_ID`       | Loader UUID                                                                         |
| `VAMPAUTH_IDEMPOTENCY_KEY` | Stable key retained for one operation and its retries; UUID for publishing/rotation |
| `VAMPAUTH_SOURCE_FILE`     | Path to original source for upload/replacement                                      |
| `VAMPAUTH_ALIAS`           | Technical loader alias                                                              |
| `VAMPAUTH_DISPLAY_NAME`    | Optional friendly loader name                                                       |
| `VAMPAUTH_PROVIDER_ID`     | linkvertise, lootlabs, workink, or linkunlocker                                     |
| `VAMPAUTH_PROVIDER_JSON`   | Provider configuration JSON, when using the downloadable recipe clients             |

## Standalone validation example

| Variable               | Use                                                                      |
| ---------------------- | ------------------------------------------------------------------------ |
| `VAMPAUTH_PROJECT_ID`  | Public 16-character project ID or project UUID; echoed in the response   |
| `VAMPAUTH_AUTH_SECRET` | Current project signing secret, supplied to your backend                 |
| `VAMPAUTH_KEY`         | Key being checked                                                        |
| `APP_DEVICE_ID`        | Stable application/device identifier; the example hashes it with SHA-256 |

Use a secret manager or private shell environment for credentials. A backend can hold the auth secret; a browser bundle or distributed Roblox script cannot keep it private.

## Inside the loader

`script_key` is a Luau input, not an OS environment variable. `VAMPAUTH` is the read-only runtime context. Neither is a replacement for a management token.

## Running the main Discord bot yourself

The repository bot expects Node 22+. It reads the website's existing .env.local unless `VAMPAUTH_ENV_FILE` selects another file; process environment values take priority.

Required: `DISCORD_BOT_TOKEN`, `DISCORD_CLIENT_ID`, and `DATABASE_URL`. Optional: `APP_BASE_URL` (defaults to <https://vampauth.com>) and `DISCORD_GUILD_ID` for test-server command registration. This is operator configuration, not something members need to use a panel. The separate utility bot has its own token and application.

## Next steps

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