> For the complete documentation index, see [llms.txt](https://griffin-ai.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://griffin-ai.gitbook.io/knowledge-base/network-participants-and-contributors.md).

# Network Participants and Contributors

The Griffin AI network thrives on the diverse roles and contributions of its participants. The ecosystem is broadly categorized into Network Participants, who are integral to the network's daily operation and utilization, and Key Contributors, who play a crucial role in supporting and enhancing the network's capabilities. 

 

<table data-full-width="false"><thead><tr><th>Role</th><th>Description</th><th>Responsibilities</th></tr></thead><tbody><tr><td><em>Network Participants</em> </td><td></td><td></td></tr><tr><td>Service Provider (SP) </td><td>Offering AI services, middleware, data sets, libraries, computation, and storage </td><td><ul><li>Provide AI services directly or act as intermediary for third-party APIs </li><li>Run Griffin AI full-node </li></ul><p> </p></td></tr><tr><td>Client Provider (CP) </td><td>Apps / DApps providing user-friendly interfaces for end users, may include account management and payment collection </td><td><ul><li>Simplify user interaction </li><li>Run either a Griffin AI full-node or utilize a Griffin AI SDK </li></ul><p> </p></td></tr><tr><td>Users </td><td>Individuals, projects, DAOs, DApps or organizations using AI models and services </td><td><ul><li>Pay for services consumed </li><li>Optional: run Griffin AI full- or light node </li></ul></td></tr><tr><td>Trust Guardians </td><td>Operator overseeing network integrity and node reputation </td><td><ul><li>Collect and monitor network activity, node availability, reputation data </li><li>Record data to reputation system </li><li>Run a Griffin AI full-node   </li></ul></td></tr><tr><td>Payment Provider </td><td><p>Per default the network is utilizing direct, peer-to-peer payment systems. In the future additional payment and escrow services might be introduced by third-party providers. </p><p> </p></td><td><ul><li>Facilitate payments between user / CP and SP.  </li><li>Provide escrow services </li><li>Run a Griffin AI full-node </li></ul></td></tr><tr><td> </td><td> </td><td> </td></tr><tr><td><em>Key Contributors</em> </td><td></td><td></td></tr><tr><td>Code and Model Creators </td><td>Individuals or teams developing code, libraries, frameworks, AI models, and ML algorithms </td><td><ul><li>Contribute to public good and Griffin AI technology stack  </li><li>Offer proprietary services to network participants </li></ul></td></tr><tr><td>Community Contributors </td><td>Individuals offering expertise, feedback (such as RLHF), and personal data </td><td><ul><li>Contribute to the advancement of Griffin AI network </li><li>Render services for specific network participants </li></ul></td></tr><tr><td>AI Agents </td><td>(Semi-)autonomous agents acting as user of Griffin AI or providing services within the network  </td><td><ul><li>Pay for services consumed </li><li>Render services on behalf of users </li></ul></td></tr></tbody></table>

Table 2: Roles within Griffin AI&#x20;


---

# 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, and the optional `goal` query parameter:

```
GET https://griffin-ai.gitbook.io/knowledge-base/network-participants-and-contributors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.