> 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/features/checkpoint-packages.md).

# Checkpoint packages, renewal, and stacking

A provider package pairs a checkpoint count with a key duration. Give users a small number of clear choices rather than several nearly identical offers.

A provider accepts up to 20 ordered links and 10 packages. Each package has 1–50 checkpoints, within the project’s effective limit, and a duration of 60–31,536,000 seconds. It can also assign the resulting key to a project key group.

Links run in order and cycle when a package needs more checkpoints than links. With links A and B, a five-checkpoint package follows A → B → A → B → A. The first usable package is the default offer.

## Renew an expired key

The original browser session can select its expired key and complete a fresh flow. The key and its binding are preserved. Banned/revoked keys cannot renew, and an already-active key does not use this expired-key renewal path.

## Stack more time before expiry

For an eligible active checkpoint key, stacking repeats its original package and adds that package’s current duration. It does not issue another key. The original provider/package must still be available.

Stacks are not available for lifetime keys, origin-less manual/legacy keys, expired keys, or banned/revoked keys. Use renewal for an expired key. The default per-key cooldown is ten minutes; the project can set 0–86,400 seconds.

## Browser session matters

Public renewal and stacking are tied to the session that owns the key. They require a fresh captcha token. A copied key by itself does not authorize those browser actions. Finish a pending Discord claim before starting another flow.

## Next steps

* [Checkpoint providers](/vampauth-docs/integrations/checkpoint-providers.md)
* [Checkpoint and Discord problems](/vampauth-docs/troubleshooting/checkpoint-and-discord.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/features/checkpoint-packages.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.