# Main entities

End-users of Yelay can be:

* Client/Project: entity that operates several pools within the vault for their end users. F.e: launchpools
* Retail end user: user of Yelay's retail apps. F.e <https://app.yelay.io/>

The main entities of Yelay's architecture are:

* Vault - smart contract (1 per asset on each supported chain) that receives user deposits  and channels them to strategies
* Pool - client's space within the vault. Each client gets a range of pool IDs to operate within given vault.  Every pool's KPIs like yield, TVL can be track separately. All retail users are assigned to a single pool within the vault.&#x20;
* Strategy - adapter to the protocol that generates yield (f.e. Morpho, Aave, Gearbox)

Image below illustrates the relationship between **User, Client, Vault, Pool and Strategies:**

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


---

# 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.yelay.io/yelay-sdk/main-entities.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.