> For the complete documentation index, see [llms.txt](https://docs.popularex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.popularex.com/iii.-popularity-ranking-and-reputation-score/pr-and-rs-graphs.md). # PR & RS Graphs Each change in Popularity Ranking (PR) and Reputation Score (RS) is recorded and stored in the blockchain, making Populárex a repository and source of historical data for these ratings. These indicators allow for the creation of graphs showing changes in popularity and public sentiment (Positive and Negative Reputation Ratings) over time on each ToP's page. This data can be useful for finding and analyzing correlations between Populárex ratings and the popularity of real-life objects of popularity or the value/popularity of assets on different markets. PR and RS rating indicators for popularity tokens can also be useful for other websites. Owners of such resources can place a special Widget on their pages, which demonstrates to their audience what society thinks of the object of popularity mentioned on the page. *This section is subject to additions and modifications. Stay tuned for updates.* --- # 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.popularex.com/iii.-popularity-ranking-and-reputation-score/pr-and-rs-graphs.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.