> For the complete documentation index, see [llms.txt](https://docs.hive.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hive.one/key-concepts.md). # Key Concepts The API and our data share some key concepts, whilst simple it is important for you to understand these properly. ### Cluster A particular community / interest group eg. Bitcoin, Ethereum, Ripple ### Score A metric out of 1000 to showing the influence of a given influencer within a particular cluster. This is created using our own algorithm using only publicly accessible data. For more info on what this means we recommend you read [this article](http://maciek.blog/influence/). With the way our algorithm currently works, every twitter account can have a score within a cluster (most will have a score of 0.0), but we rarely collect or record this. ### Rank Only accounts with high scores will have ranks. Unlike scores, not everyone has a rank. We use algorithms to filter out irrelevant people within clusters. Accounts without ranks will have the following data representation in their responses:`rank: null` ### People Our API treats people differently from other types of influencers (Companies, bots). For that reason ranks using `rank_type=personal` may be different from the ranks given in the endpoint `rank_type=all` The ranks displayed on the [hive.one](https://hive.one) homepage are using `rank_type=personal` ### Twitter ID A unique series of numbers corresponding to a twitter account. ### Twitter Screen Name The username of a Twitter account. We never include ‘@’ symbols --- # 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.hive.one/key-concepts.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.