> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/workspace/chat/token-usage-and-file-storage.md).
# Token usage and File Storage
Every conversation now shows your real-time costs at the top right of each Chat. See the total cost, average per message, and conversation length so you know exactly where your budget is going. See how much storage your uploaded files use. The file count and total size are displayed together, so you can easily keep track of your storage usage.
### Credit usage
Start a New Chat or continue the old one, send your prompt, and click on **Usage** to find out what it cost in AI Workspace credits.
### File storage
The uploaded files and the storage space they use are displayed in the top-right corner of your chat:
### Deleting Files in Chat
1. Find the file usage indicator in the top-right corner and click it.
2. Hover over the file you want to delete and click the three-dot menu.
3. Select Delete to remove the file.
{% hint style="info" %}
Currently, deleting multiple files at once in a chat is not supported.
{% endhint %}
---
# 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://docs.nexos.ai/workspace/chat/token-usage-and-file-storage.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.
