> 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/first-project.md).

# Your first project

You need a Vampauth account and a script you can test.

1. Open the [dashboard](https://vampauth.com/dashboard) and create a project.
2. Choose the default key duration and whether keys should bind to one device.
3. Add your script, connect its loader to the project, and publish it.
4. Create a test key. For a timed manual key, the default is **On first use**.
5. Copy the loader snippet from the dashboard. Put the test key in `script_key` and run it.
6. Check the key details. A successful run should show usage; a first-use key should now have an activation time and expiry.

Keep a copy of your original script. Publishing stores protected output, so downloading the stored payload later does not recover the original source.

## Let people get a key

For a free script, connect a checkpoint provider and add a package. A package says how many checkpoints the user completes and how long the key lasts. Open your project's flow URL and try the whole path before sharing it.

For paid or private distribution, create keys manually or from your backend with the management API. You don't need a checkpoint provider to issue a key.

## Share the right link

Give players the loader snippet and your project's key-page URL. Keep management tokens, project auth secrets, and provider credentials on your side.

## Next steps

* [Loader](/vampauth-docs/development/loader.md)
* [Keys and expiry](/vampauth-docs/features/keys-and-expiry.md)
* [Checkpoint providers](/vampauth-docs/integrations/checkpoint-providers.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/first-project.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.