> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/trading/trading-fees/lit-fee-credits.md).

# LIT Fee Credits

The LIT Fee Credits program is designed to support market participants making use of Premium/Advanced Accounts that have not yet committed to staking. Instead of staking the full amount required for a higher discount tier, users can buy Credits, which count toward the desired fee-discount and rate-limit tier.

For example, a participant with 100,000 LIT staked may buy 200,000 LIT of Fee Credits to reach the 300,000 LIT tier.

#### How it Works

Participants must acquire LIT if they do not already hold it and navigate to the LIT Fee Credits section on the Staking page. There, they can select the desired credit amount and duration, which determine the applicable trading tier. Upon confirming an L1 signature and completing the upfront LIT payment, the selected tier is activated.

All proceeds from the LIT Fee Credits program are distributed to LIT stakers. The upfront fee is streamed as daily rewards over the full duration of the access period.


---

# 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://docs.lighter.xyz/trading/trading-fees/lit-fee-credits.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.