> For the complete documentation index, see [llms.txt](https://starterpack.onest.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://starterpack.onest.network/readme/roles-you-can-play.md).

# Roles You Can Play

An entity can play various roles on ONEST, the primary roles are

**Provider Platform:** If you aspire to broaden the reach of the training, scholarships, jobs, and mentorship opportunities you offer, we invite you to join the network as a Provider Platform.\
\
**Provider**: If you’d like to be onboarded on an existing provider platform as one of the providers of the training, scholarships, jobs, and mentorship opportunities, we invite you to join the network as a Provider.\
\
**Seeker Platform**: If you seek to explore the vast array of training, scholarships, jobs, and mentorship opportunities available within the network, we encourage you to join as a Seeker Platform.\
\
**Seeker**: If you’d like to consume the information made available by the ONEST network through any of the seeker platforms, you can join as a seeker. \
\
**Technology Service Provider**: If you choose to enable other organizations to join this network through your technology, business or onboarding services, this role will suit you the best.\
\
You have the flexibility to choose one of the aforementioned roles or even assume more than one role within the network, enabling you to actively engage in and benefit from the diverse opportunities provided by the network.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://starterpack.onest.network/readme/roles-you-can-play.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
