# Ecosystem

#### Layer 1 — Users & Organizations

<figure><img src="/files/CXFHGRJeyiFahqhesFeF" alt=""><figcaption></figcaption></figure>

Every organization gets its own wallet and can independently issue and verify credentials.

***

#### Layer 2 — Ecosystems

The platform admin can designate any organization as an Ecosystem Lead. That lead then governs an ecosystem by inviting other organizations to join as Ecosystem Members.

<figure><img src="/files/oRZSODVLv6zdFKI5msrd" alt=""><figcaption></figcaption></figure>

The invite flow works in two hops: admin → lead organization, then lead → member organizations. Organizations that reject the invite remain outside the ecosystem with no access to its data.

{% hint style="info" %}
You can make code blocks [span the full width of your window](https://gitbook.com/docs/creating-content/blocks#full-width-blocks) by clicking on the **Options menu** <i class="fa-grip-dots-vertical">:grip-dots-vertical:</i> icon in GitBook next to the block and choosing **Full width.**
{% endhint %}


---

# 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://docs.credebl.id/docs/references/platform-apis/ecosystem.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.