> For the complete documentation index, see [llms.txt](https://anonymous-humanoid.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anonymous-humanoid.gitbook.io/docs/getting-started-hardware.md). # Getting Started (Hardware) This section covers the hardware required to build the Humanoid\* humanoid robot, from sourcing components to fabrication and assembly. Use the pages below as a step-by-step reference for preparing the parts and tools needed for the build:

		Cover image
Bill of Materials	Complete list of mechanical, electrical, and purchased components	image.png	Bill of Materials
Tools	Recommended tools and equipment for fabrication and assembly	IMG_7286.JPEG	Tools
3D Printing	Printing files, material recommendations, and preparation guidelines for printed components	IMG_7288.JPEG	3D Printing
Assembly Instructions	Step-by-step instructions for assembling the humanoid hardware	image.png	Assembly Instructions
Waterjet / Embedded Metal Manufacturing	Fabrication instructions for the waterjet-cut and embedded metal components used in the robot	IMG_7289.JPEG	Waterjet/Embedded Metal Manufacturing

--- # 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://anonymous-humanoid.gitbook.io/docs/getting-started-hardware.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.