> For the complete documentation index, see [llms.txt](https://faq-liquidandgrit.gitbook.io/products-and-services/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq-liquidandgrit.gitbook.io/products-and-services/extras/q-and-a.md).

# Q\&A

Answers to some of our most asked questions.

<details>

<summary>What type of subscriptions do you offer?</summary>

We offer subscriptions on the enterprise level. Subscriptions are tailored to your team's individual needs – get in touch and we can put together a plan that works best for you.&#x20;

</details>

<details>

<summary>Do you offer free trials?</summary>

We do not offer free trials. However, we are happy to answer any additional questions you may have about our products and services to better determine what value we can provide you.

</details>

<details>

<summary>Do you provide individual subscriptions?</summary>

We do not provide individual subscriptions – subscriptions are designed for teams and sold on an enterprise level.

</details>

<details>

<summary>Do you offer students free or special pricing?</summary>

Unfortunately, we do not provide any of our paid services to students or academic entities for free or discounted rates. Nevertheless, you are more than welcome to utilize and reference any publicly accessible data from our [website](https://www.liquidandgrit.com/), such as [sample reports](https://www.liquidandgrit.com/resources/) and our [blog](https://blog.liquidandgrit.com/).

</details>

<details>

<summary>What is the minimum price of a subscription?</summary>

We provide customized platform subscriptions based on customer needs – contact us to discuss a plan that works best for you.&#x20;

</details>

<details>

<summary>Do you offer one-time access to the platform?</summary>

We do not. Liquid & Grit products are subscription-based and focused on supporting our customers’ ongoing performance goals. For one-off projects, explore our [**Custom Projects**](/products-and-services/information-by-product/custom-projects.md) sections.

</details>

<details>

<summary>What type of custom research do you do?</summary>

Our custom research projects help teams uncover deep insights on important, specific topics not currently covered by our reports. Examples include full app deconstructs, economy analyses, app monetization reviews, market opportunity assessments, and player motivation studies.&#x20;

Check out more information in our [**Custom Projects** ](/products-and-services/information-by-product/custom-projects.md)section.

</details>

## Have more questions? We're here to answer!

If you don't see the answer to your question on these pages or want to contact us, fill out the form below or email us at <support@liquidandgrit.com>.

{% embed url="<https://liquidandgrit.typeform.com/to/C4SM2LiS?typeform-source=www.liquidandgrit.com>" %}


---

# 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://faq-liquidandgrit.gitbook.io/products-and-services/extras/q-and-a.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.