> For the complete documentation index, see [llms.txt](https://docs.veerobot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veerobot.com/readme.md).

# Introduction

Welcome to the official documentation hub for VEEROBOT's robots.

If you have **BeetleBot Plus**, start with the [**Tutorials**](/tutorials/beetlebot-plus.md) for step-by-step labs, or the [**BeetleBot Plus**](/ros-robots/beetle-bot-plus.md) overview for specs and unbox. [**VEEStack**](/veestack/veestack.md) is the short software reference.

## 🚀 Quick Links

### 🎓 Tutorials

Numbered courses by robot (self-contained lessons).

* [**Tutorials home**](/tutorials/tutorials.md)
* [**BeetleBot Plus tutorials**](/tutorials/beetlebot-plus.md), Operate, Chassis, Lidar & 2D nav

### VEEStack

How to connect, ARM, maps, Foxglove, and the HTTP API.

* [**Operate**](/veestack/veestack.md), operator book
* [**Research**](/veestack/research.md), ROS 2 topics, RViz, HTTP API, webhooks
* [**Plugins**](/veestack/plugins.md), what a license unlocks

### 🤖 ROS Based Robots

* [**🐺 Wolf Robot**](/ros-robots/wolf-robot.md): ROS 2 teaching platform (URDF, Gazebo, SLAM tutorials).
* [**🪲 BeetleBot Plus**](/ros-robots/beetle-bot-plus.md): User manual, unbox, battery, first drive, ROS 2, RViz, HTTP API.
* [**🐞 Beetle Bot**](/ros-robots/beetle-bot.md): ROS 2 teaching manual.

### 🕹️ Arduino Based Robots

* [**🚜 Micro:Xbot**](/arduino-based-robots/micro-xbot.md): LEDs, sensors, motors, line following and obstacle avoidance.

## 📖 How to Use This Documentation

Use the sidebar navigation to jump directly to the robot platform you are working with. Each section contains step-by-step instructions, code snippets, and configuration guides to help you get your robot up and running quickly.

Happy Building! 🛠️


---

# 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.veerobot.com/readme.md?ask=<question>&goal=<user_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.