# SPARKLET Utility and Demand

\
Ecosystem participants in the open economy including Upland Players, Upland Entrepreneurs and Creators, 3rd Party Developers and Brand/Partners, all require SPARKLET for a variety of functions:

### Upland Players

Require SPARKLET to build and develop their properties and neighborhoods. Coming in 2024, players will also use SPARKLET to charge their virtual vehicles for means of travel (a core metaverse mechanic) or leisure (e.g. racing).

### Upland Entrepreneurs and Creators

Require SPARKLET to build shops, factories, and showrooms to facilitate their “Metaventures” – player-owned businesses – that serve as specialized primary and secondary market shops in the economy. Used as a resource for the creation of user-generated content (“UGC”) NFTs, Upland Entrepreneurs also use SPARKLET for the no-code manufacturing (minting) of virtual assets that can be traded with other players.

### 3rd Party Developers

Require SPARKLET to establish map presence via “Dev Shops”  (unique constructions which allow players to discover and launch the developers’ offering from within the Upland map) for visibility. SPARKLET fuels the implementation of their zero-code web3 and NFT strategy using the Upland platform

### Partners/Brands

(e.g. FIFA, NFLPA, UNICEF, Stock Car Pro Series) Need SPARKLET in a similar fashion to Upland Entrepreneurs. The partner/brand creates virtual assets that would be offered to players for purchase during events, in mini-games, and competitions. SPARKLET powers the partner’s/brand’s metaverse strategy for fan engagement, co-creation, and monetization in the open metaverse.

<br>


---

# 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://guides.upland.me/sparklet/sparklet-white-paper-july-2023/sparklet-utility-and-demand.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.
