# Use Case

### Use Cases Powered by AIGI Network <a href="#ff9d" id="ff9d"></a>

AIGI Network is a foundational layer that enables a wide range of use cases across AI and Web3. Here are a few examples:

#### 🧩Decentralized AI Agent Ecosystems <a href="#dbb2" id="dbb2"></a>

Developers can build and train AI agents directly within the AIGI ecosystem, with models attributed, rewarded, and composable — enabling a new generation of trustless, cooperative agents.

#### 💡Data Contributor Marketplaces <a href="#id-5f6c" id="id-5f6c"></a>

Experts, curators, and communities can form **DataSlots** to contribute specialized, high-quality datasets (e.g. legal, scientific, cultural), earn attribution credit, and generate long-term passive income.

#### 🌍AI Model-as-a-Service (MaaS) <a href="#id-817c" id="id-817c"></a>

Models trained on AIGI Network can be deployed as verifiable services, with every output traceable to its data origin— solving black-box AI deployment for enterprises and regulators.

#### 🚧Compliance-ready AI <a href="#id-9a08" id="id-9a08"></a>

With full attribution and auditability, AIGI enables compliant AI systems — useful in healthcare, finance, and other regulated industries.

### Why AIGI Network Matters <a href="#baa0" id="baa0"></a>

* **Verifiability**\
  → No more black-box models. Every output is traceable to its origins.
* **Fairness**\
  → Contributors are rewarded proportionally to the value they create.
* **Scalability**\
  → Tentacle Procedure enables massive scale through distributed compute.
* **Openness**\
  → Anyone can contribute data, models, compute, or validation — and earn.


---

# 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://aigi-protocol.gitbook.io/aigi-protocol/overview/user-facing/aigi-network/use-case.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.