> For the complete documentation index, see [llms.txt](https://docs.botto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.botto.com/miscellaneous/team.md). # Acknowledgements While Botto is still in its infancy, creating the decentralized autonomous artist has been a great collaborative effort between multiple teams and contributors. The teams from [ElevenYellow](https://elevenyellow.com) and [Carbono ](https://carbono.com)have spent the better part of the year concepting, planning, and iterating on this very first version of Botto. The team and growing community are also eternally grateful for the art engine that was created, tweaked and then made autonomous by the generative artist [@quasimondo](https://twitter.com/quasimondo). Needless to say, this project has certainly not been a single collective's effort. Countless contributors have helped by providing their own interpration of who Botto is and why Botto matters. We are thankful for the continued support of all early contributors. You are visionaries of Botto. --- # 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://docs.botto.com/miscellaneous/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.