> For the complete documentation index, see [llms.txt](https://docs.lsr.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsr.finance/token/about.md).
# About
**LSR (LaserEyes)** is a **utility token** behind LSR Finance
LSR will be used as
* a payment to reduce swap fees at findX
* a payment to verify token at LaserScan
* a payment to vote for token at LaserScan
LSR is available at:
* [BNB chain](https://bscscan.com/token/0x1cb9ca00538265a22e56b758026948608ba5d86f) (main): 0x1cb9ca00538265a22e56b758026948608ba5d86f
## Supply
* LSR has **fixed supply** (max supply is limited by 1,000,000,000 LSR)
* LSR has **mint** (occurs monthly and increases total supply from 400,000,000 LSR to 1,000,000,000 LSR over 20 years).
* LSR has **no rebase** (supply doesn't change with respect to price)
## Trading
* LSR **is traded at PancakeSwap & BiSwap**
* LSR has **0 buy / sell fees & taxes**
* LSR has **recommended slippage 0.5%-1%**
---
# 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://docs.lsr.finance/token/about.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.