# Ecosystem

| Role                                         | Key Needs                                                                                           | Value / Contribution to the Ecosystem                                                             |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **AI Developers / Individual Developers**    | Low‑friction access to multiple foundation models; elastic GPU resources for training and inference | Generate API and compute demand, driving SPT consumption and platform traffic                     |
| **Enterprises & AI Teams**                   | Large‑scale model training, cost‑controlled compute rentals, unified billing                        | Provide stable, high‑value orders that expand Hash Forest and the DePIN network                   |
| **Algorithm / Model Providers**              | Rapidly wrap proprietary models into APIs and monetize usage                                        | Enrich the platform’s model catalog, boosting application diversity and overall call volume       |
| **GPU Compute Node Providers**               | Connect idle or commercial GPUs to earn SPT mining rewards                                          | Expand decentralized compute capacity, ensuring network elasticity and low latency                |
| **End‑Application Consumers (B2B / B2C)**    | Use AI applications powered by the platform (chatbots, generative content, analytics, etc.)         | Create real business scenarios and cash flow, validating platform technology and commercial value |
| **Web3 Investors & Governance Participants** | Stake/hold SPT for yield and participate in governance voting                                       | Supply liquidity and governance vitality, supporting long‑term ecosystem growth                   |


---

# 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://stempoint.gitbook.io/stempoint/getting-started/publish-your-docs.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.