> For the complete documentation index, see [llms.txt](https://babysoraai.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://babysoraai.gitbook.io/whitepaper/about-team.md). # About Team We assembled a large team divided into 5 small groups to implement BabySora. The special thing we want to mention is that the majority of members are knowledgeable about both the cryptocurrency market and AI technology. This is an advantage so we can apply AI technology to projects effectively and safely. All members work effectively with the aim of moving BabySora forward and bringing benefits to all participants In the near future after launch, we will add additional personnel in several Asian and European countries. We aim to provide the best support for users in each country to limit language and time differences. You can apply if you like the project. We will post specific information on the main pages to keep you updated. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://babysoraai.gitbook.io/whitepaper/about-team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.