# Example Use Cases

**Enterprise MCU Example:**\
Now imagine an automotive manufacturer with tens of thousands of vehicles in storage, each equipped with advanced IoT microcontrollers and connectivity modules. While parked, these vehicles’ MCUs and bandwidth go unused. Idle Network activates that idle potential, connecting them into decentralized IoT reward ecosystems (for example, networks rewarding devices for real-time environmental sensing or secure data transmission). The earned tokens are routed into Idle MetaVaults, where they are diversified into auto-compounding DeFi strategies. At scale, this transforms fleets of inactive vehicles into distributed yield generators, offsetting operational costs and turning downtime into measurable income.\
\
**Consumer IoT Example:**\
Consider a smart thermostat installed in a household. Most of the time, its microcontroller unit (MCU) sits idle, only occasionally adjusting heating or cooling. Through Idle Network, that dormant compute capacity and network connection can be contributed to decentralized IoT reward networks. The thermostat earns tokens for tasks such as lightweight data validation or sensor mesh relaying. Idle’s MetaVaults automatically aggregates these rewards, converts them into a stable or blue-chip crypto asset, and compounds them in DeFi lending protocols. For the homeowner, the thermostat doesn’t just save energy—it generates a passive income stream in the background.


---

# 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.idlenetwork.com/idle-mcu-and-iot-marketplace/example-use-cases.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.
