> For the complete documentation index, see [llms.txt](https://docs.lumi-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumi-ai.com/using-lumi/lumi-use-cases/data-exploration.md).

# Data Exploration

This category helps users investigate and better understand their datasets through basic statistics, relationships, and visualizations.

## **Data Search & Filtering**

### Retrieving specific details such as categories, descriptions and basic types.

**Purpose**: To provide a high-level summary and quick access to key data points, such as categories, counts, and relationships along with the ability to apply filters, search for specific information, or focus on particular subsets of data.

{% hint style="info" %} <mark style="color:blue;">**Use Case:**</mark> To give users a high-level overview of their available data, helping them quickly understand the structure, types of categories, and key fields for inventory, sales, or product analysis. This is especially useful when beginning data analysis or exploratory data queries.
{% endhint %}

> **Typical Prompts**:
>
> * "List the total number of products in each category."
> * "For customer ABC, show all orders with status 'Not Paid Yet'."
> * "List all products with stock levels below XX units."
>
> **Example Output: What are all the item categories and ids we have?**

<figure><img src="/files/nBdnMdrZdQOr4wIvEAVY" alt=""><figcaption></figcaption></figure>

> **Example Output: Who are all our distinct customers?**

<figure><img src="/files/R4Qmcvta0XHskExDPqy0" alt=""><figcaption></figcaption></figure>

> **Example Output: For CUST002, are there any orders with order status 'Not Paid Yet'? Include relevant details.**

<figure><img src="/files/LXSuGrfk5rZtXR9Nmm4u" alt=""><figcaption></figcaption></figure>

## **Basic Aggregation**

### Provide essential aggregations like average, sum, min, max, and count.

**Purpose:** Lumi AI provides powerful aggregation capabilities, enabling users to calculate essential business statistics such as maximum, minimum, sum, average, profit, revenue, and costs. This allows business users to quickly analyze performance, financial metrics, and operational efficiency without requiring technical expertise in SQL or Python.

{% hint style="info" %} <mark style="color:blue;">Use Case:</mark> A procurement manager at a manufacturing company wants to analyze total procurement costs, average supplier costs, and identify the best and worst-performing suppliers.
{% endhint %}

> **Typical Prompts:**
>
> 1. *"What was the total revenue and average profit for each product category in YTD?"*
> 2. *"What is the highest operational cost category by department for Q1 2024."*
> 3. *"Give me the total procurement costs for all suppliers in 2023, and identify the supplier with the lowest cost."*
> 4. *"What is the average revenue per region in Q2 2024, and which region had the highest revenue?"*
>
> **Example Output: What is the average weekly quantity sold of item 1001 in 2023?**

<figure><img src="/files/NnbrtfO6rVHy4ZFCmdkR" alt=""><figcaption></figcaption></figure>


---

# 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.lumi-ai.com/using-lumi/lumi-use-cases/data-exploration.md?ask=<question>&goal=<endgoal>
```

`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.
