> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/openstocks-manual-v2/06-ecosystem.md).

# 06 Ecosystem

The Ecosystem page lists the chains, stablecoins, protocols, exchanges, and wallets that work with OpenStocks. Use it to find services that connect to pre-IPO tokens.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/P1XCV2HhxyjWq2fZ16lk/Unknown%20image)

1. **Category filters**\
   Show one category at a time, with the number of entries in each.
2. **Status**\
   Shows whether an integration is live, planned, or coming soon.
3. **Description**\
   Explains what the partner does and how it connects to OpenStocks.
4. **Category tags**\
   Show which categories an entry belongs to.

## Categories

The six categories are Chain, Stablecoin, RWA, Yield, Trading, and Wallet. Select All to see every entry. An entry can be in more than one category, so the category counts add up to more than the total.

## Cards

Select a card to open the partner's site. Read the status and the description together to see where each integration stands.

## Key entries

The Chain entry is BNB Chain, where every pre-IPO token settles. The Trading entries are the exchanges in the trade dialog, and the Wallet entries are the wallets confirmed to hold the tokens. Both are described in **Placing a trade**.


---

# 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.allocations.com/openstocks-manual-v2/06-ecosystem.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.
