> For the complete documentation index, see [llms.txt](https://lucia-protocol.gitbook.io/lucia-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucia-protocol.gitbook.io/lucia-protocol/the-lci-token.md). # The LCI Token LCI serves as a crucial secondary token within the LUCIA Protocol's ecosystem, engineered specifically to reward early adopters and contribute to the platform's liquidity. When users stake their LCI tokens, they are converted into stLCI, which subsequently qualifies them for a portion of the revenue generated from various fees within the Protocol. **Liquidity Provision through LCI** Beyond staking, LCI offers another utility: liquidity provision. Users can contribute to the LUCI liquidity pool to receive LCI tokens in return. By doing so, they not only enhance the overall liquidity of LUCI but also gain the opportunity to stake their newly-acquired LCI for additional rewards through stLCI. By encompassing both incentive mechanisms and liquidity provisions, LCI acts as a powerful tool to engage and reward users, thereby fostering the health, liquidity, and overall robustness of the LUCIA Protocol. --- # 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://lucia-protocol.gitbook.io/lucia-protocol/the-lci-token.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.