> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-geolocation-credit/lct-credit-consumption-per-device.md).
# LCT - Credit Consumption per Device
The **Overview of credit consumption per device** shows how geolocation credits are being used by the individual LCT devices within the tenant.
This view helps identify devices with higher or lower geolocation usage and makes it easier to understand how the available tenant credit capacity is being consumed.
## Steps to View Credit Consumption per Device
1. Open the **Cockpit Menu**.
2. Select **Administration**.
3. Click **Geolocation Credit**.
4. Scroll to **Overview of credit consumption per device**.
## Information Displayed
The table lists LCT devices together with their geolocation-credit consumption information.
Use this section to compare device usage and identify devices that are consuming credits faster than the rest of the fleet.
Select the **information icon** in the section to view additional details about per-device credit consumption.
---
# 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.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-geolocation-credit/lct-credit-consumption-per-device.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.
