> For the complete documentation index, see [llms.txt](https://modster-customs.gitbook.io/modster-customs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://modster-customs.gitbook.io/modster-customs-docs/purchases-and-tebex/15-subscriptions.md).

# Subscriptions

## What does a Modster Customs subscription include?

The exact subscription benefits are determined by the subscription product description.

For example, if your subscription advertises access to all vehicles in a specific category, only the products covered by that description are included.

## When does my subscription renew?

Check the subscription information shown at checkout and in your Tebex account.

## What happens when my subscription expires?

Access to subscription-only products/features may end when the subscription expires, according to the subscription terms.

## Can I cancel my subscription?

Use the subscription management options provided by Tebex, or contact support if you need assistance.

## Important

Always publish your current Tebex subscription terms here so customers have one authoritative source.


---

# 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://modster-customs.gitbook.io/modster-customs-docs/purchases-and-tebex/15-subscriptions.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.
