# Monitoring

#### API Usage Dashboard Documentation

This documentation provides an overview of the [**API Usage Dashboard**](https://cloud.segmind.com/console/usage?utm_source=docs), designed to help users monitor and manage their API consumption. The dashboard displays information on API usage, helping you keep track of requests and associated costs. It might take upto two hours before the latest data is available on this dashboard.

**Overview of the Dashboard**

1. **Credits**: This shows the total credit balance currently available in your account. .
2. **Requests Today**: Displays the number of API requests made on the current day. This metric resets at the beginning of each new day.
3. **Total Requests (All Time)**: Shows the cumulative number of API requests made since the account was created. This gives an overview of the total usage over time.

**API Usage Breakdown**

The **API Usage Breakdown** section provides detailed insights into the API requests, broken down by model routes, including the associated costs and the number of inferences made.

* **Select a Date Range**: You can filter the data by selecting a specific date range to analyze usage and costs within that period.
* **Model Route**: Indicates the specific API model or service used. Each route corresponds to a different functionality or type of model available on the platform.
* **Amount**: The cost incurred for using the specific model route. This is the amount charged per inference or API request.
* **Date**: The date on which the API requests were made for the specific model route.
* **# of Inferences:** The total number of inferences or API requests made using the specific model route on the given date.


---

# Agent Instructions: 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:

```
GET https://docs.segmind.com/api-reference/monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.