> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/account-settings.md). # Account settings Find your account ID and balances, and save an OctaneBench score for cost estimates. Click your name or account icon at the bottom of the sidebar, then open **Account Settings**. ## Save your OctaneBench score Enter a whole number greater than 0 in **Your OB Score** under **OctaneBench Reference**. The value saves automatically and is reused in the [Cost Calculator](/docs/web-app/cost-calculator.md) and job creation estimates in this browser. If you do not know your score, **Find Estimate** opens OctaneBench results, and **Download Benchmark** opens the OctaneBench download page. ## Find account details The account summary shows your name, account role when assigned, ID, and email address. Click the ID to copy it, or click the partly hidden email address to copy the full address. Under **Render Credits** and **Render Tokens**, **Spent** shows the total used and **Available** shows the remaining balance. **Activity** lists the totals for uploaded scenes, created jobs, and rendered frames. Use **Download Job History** below the summary to [export job details](/docs/web-app/billing-and-job-history.md#export-job-history). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://know.rendernetwork.com/docs/web-app/account-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.