> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/about-xyo/xyo-101/build-operate-and-scale-with-xyo.md).
# Build, Operate & Scale with XYO
> ⚠️ This section is currently in progress. Some tools and documentation are not yet available because XYO Layer One mainnet is launching later in 2025, and core APIs and SDKs are still in development.
This section is for those who are ready to go beyond understanding XYO — and start building with it.
Whether you're setting up a node, launching a sovereign chain, or integrating with the XYO Protocol, this level will give you the tools and guidance to take real action.
### Where to Go Next: How-to Guides
---
# 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.xyo.network/about-xyo/xyo-101/build-operate-and-scale-with-xyo.md?ask=&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.
