> 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/choose-an-integration.md).

# Choose an integration

## Roblox scripts

Use a dashboard loader. It checks the key, selects the payload, downloads the script, and sets up the runtime context. You don't add a second key-check request inside the uploaded script.

## Your own app

Use standalone signed key checks from your backend. They return an access decision, without script delivery or loader leases.

## Storefronts and automation

Use the v2 management API to manage projects, keys, groups, providers, loaders, collaborators, and hardware bans. Create a scoped bearer token in Settings → Developer API.

## Discord communities

A project panel lets members save a key, see its details, reset hardware when allowed, and get the selected loader snippet. A separate Discord claim requirement can sit at the end of a checkpoint flow.

| Credential                      | Used for                                                 |
| ------------------------------- | -------------------------------------------------------- |
| User's key                      | Running a keyed loader or checking that user's access    |
| Project auth secret             | Signing standalone validation requests from your backend |
| Management bearer token         | Server-side v2 resource management                       |
| Provider credential             | That provider's checkpoint integration                   |
| Discord application credentials | Optional project-specific auto-join setup                |

These credentials aren't interchangeable. The old account Client Secret is not a v2 bearer token.

## Next steps

* [Loader](/vampauth-docs/development/loader.md)
* [Standalone key check](/vampauth-docs/api-reference/key-check.md)
* [Management API v2](/vampauth-docs/api-reference/management.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/choose-an-integration.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.