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

# Expanding the Ecosystem

*We aim to continually expand our ecosystem by introducing new financial products and services that cater to evolving market needs. Through strategic partnerships and open development, we enhance the platform's capabilities and reach.*

## <mark style="background-color:purple;">**Expand Financial Products and Services**</mark>

* Introduce additional products such as P2P trading, debit cards, lending solutions, and a launchpad for new projects.
* Develop connections between individual features and products within the ecosystem to create seamless experiences.

## <mark style="background-color:purple;">**Create an Open API for Developers**</mark>

* Stimulate the creation of third-party applications and tools within the EVEDEX ecosystem.
* Encourage innovation and collaboration among developers.

## <mark style="background-color:purple;">**Foster Strategic Partnerships**</mark>

* Collaborate with industry leaders to enhance the ecosystem's capabilities and reach.
* Improve interaction with public speakers and opinion leaders to increase mass adoption.


---

# 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.evedex.com/strategic-approach/expanding-the-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.