> For the complete documentation index, see [llms.txt](https://amore.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amore.gitbook.io/wiki/whitepaper/token-economics/amore-overview.md). # Amore Overview The $AMORE token is a fixed supply token that runs natively on Binance Smart Chain’s high-performance blockchain. Thanks to this the system can execute multiple required on-chain actions with high speed and without any charges. One thing important to note here is that Amore is a completely decentralized platform. Therefore, users can enhance and add newer features and functions to the platform from time to time. Some other advanced features are already in the pipeline. We will regularly publish updates to keep every member of the community up to date through our social media channels. Amore is on the journey to change the online dating experience for you! Be a part of this journey by joining us. --- # 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://amore.gitbook.io/wiki/whitepaper/token-economics/amore-overview.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.