> For the complete documentation index, see [llms.txt](https://whitepaper-en.wellthverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper-en.wellthverse.com/partners.md).

# 11. Operating Entity, Partnerships, and Community Structure

**Operating Entity**

| **Company**            | **Role**                                                            |
| ---------------------- | ------------------------------------------------------------------- |
| **Pixela Corporation** | Project owner, service operator, device development & manufacturing |

***

**Partnership Strategy**

WellthVerse actively seeks to explore and execute various forms of partnerships, including:

* **Medical & Research Institutions**
  * Providing access to Wellness Data NFT
  * Collaborative research on correlations in health data
  * Corporate licensing for medical institutions
* **Fitness & Healthcare Companies**
  * Offering benefits through WELV token and NFT integrations
  * Joint campaigns (e.g., exclusive NFTs, promo codes)
* **Retail & E-Commerce Companies**
  * Product collaborations utilizing WellthVerse NFTs and WELV tokens
  * Reward-based campaigns tied to wellness improvements
* **Other Web3 Projects**
  * Design and skin collaborations with external NFT projects
  * New use cases through integration with GameFi and SocialFi ecosystems

***

#### Community Structure

WellthVerse will also promote a robust community-driven framework, including:

* Engagement communities centered on Discord and X (Twitter)
* Grassroots fan-building via exclusive NFT distributions and special events for early participants
* Future introduction of an Ambassador Program and a Community DAO funding system


---

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

```
GET https://whitepaper-en.wellthverse.com/partners.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.