> 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/authentication.md). # Authentication You will need an API key to use our API. If you don't have an hive.one account click here to sign up for one: Once you've signed up (or if you already had an account) click here to get your API key To use your API key you must set the `Authorization` HTTP header like so: ``` Authorization: Token ``` ## Rate Limits To ensure a consistent experience for all API users, our endpoints are rate limited. When making requests with an API key you are allowed to make **2 requests per second** If you exceed your rate limit all requests will return with a `420` status code. ### Tips to avoid being Rate Limited #### Caching We recommend to cache our data in your applications to ensure you are not requesting the same data unnecessarily Our data updates every 24 hours. #### ETags Our endpoints will return with an `ETag` in the HTTP headers. We recommend using this `ETag` to check if your data needs a refresh when updating your cache. Find out more[ here](/using-etags.md) --- # 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/authentication.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.