> For the complete documentation index, see [llms.txt](https://docs.luasec.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luasec.org/licensing/ad-rewards.md).
# Ad rewards
Let users **earn a temporary key** by passing through ad links. They complete a few checkpoints, and on the last one Luasec mints a temporary key and drops them on a page to copy it.
## How it works
1. A user opens your getkey page: `https://luasec.org/getkey/`.
2. They pass ***n***** checkpoints:** each one wraps a callback in an adlink provider.
3. On the **final** checkpoint, the server verifies the provider's anti bypass proof, mints a key valid for `rewardHours`, and shows it.
## Providers
| Provider | Notes |
| --------------- | --------------------------------------------------------------------------------- |
| **Linkvertise** | Needs your Linkvertise account id (and an API token for antibypass verification). |
| **Lootlabs** | Mints a content locker link via the Lootlabs API and needs your API key. |
| **Work.ink** | Needs your Work.ink API key. |
You can chain multiple providers across checkpoints.
## Setting it up
On your project's **ad-reward** settings:
* **Enable** the gateway.
* **Checkpoints:** how many steps (1–10).
* **Providers:** which provider(s) to use across the steps.
* **Reward hours:** how long the minted key lasts.
* **Provider credentials:** your account id / API keys for the providers you use.
## Notes
* Adreward keys are ordinary keys with an expiry. They're HWID locked and bannable like any other.
* Keep `rewardHours` modest because users can re-run the flow to renew.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.luasec.org/licensing/ad-rewards.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.