> For the complete documentation index, see [llms.txt](https://docs.eitherway.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eitherway.ai/documentation/ecosystem-and-integrations/a-connected-build-environment.md). # A Connected Build Environment #### Taken together, these integrations form the infrastructure layer behind Eitherway. They are not there for optics. They are there because builders need real systems underneath the things they create. Wallets, payments, analytics, launch rails, liquidity, onchain execution, runtime support, and ecosystem access all shape whether an app can move from prompt to something usable in the market. Eitherway is built to reduce how much of that the user has to assemble manually. The result is a more connected build environment, where the builder can focus more on the product, the workflow, and the use case, while the required infrastructure sits closer to the point of creation. --- # 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.eitherway.ai/documentation/ecosystem-and-integrations/a-connected-build-environment.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.