> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/ecosystem-tools/ecosystem-example.md).
# Ecosystem example
**Clarity Partners** ecosystem is a privacy conscious ecosystem of partners using Identity Clarity KYC products.
EquiNET credit bureau as the ecosystem administrator is responsible for specifying governance rules, providing branding and maintaining the [ecosystem website](https://bank-demo.dock.io/partners).
Administrator invites ecosystem participants, in this example:
* Forsur - biometric credentials provider
* Quotient - credit union
* EquiNET - credit bureau
* UrbanScape - apartment company offering upscale rentals
{% hint style="info" %}
Ecosystem administrator can be a participant in their own ecosystem.
{% endhint %}
Administrator is also responsible for assigning the credential schemas and verification templates that will be used by the participants.
Clarity partners ecosystem has 4 credential schemas:
* ForSur - Biometric Check, that can be used by ForSur, Quotient and UrbanScape.
* ForSur - Biometric Enrollment, that can be used by ForSur.
* Quotient - Bank Identity W/ Biometrics, that can be used by Quotient and UrbanScape.
* EquiNet - Credit Score, that can be used by EquiNet and UrbanScape.
Clarity partners ecosystem has 2 verfication templates, that can be used by all participants.
* Quotient Loan Verification - Bank Identity, Biometrics, and Credit Score
* UrbanScape Credit Score Verification- Credit Score
---
# 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://docs.truvera.io/truvera-workspace/ecosystem-tools/ecosystem-example.md?ask=&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.
