> For the complete documentation index, see [llms.txt](https://wiki.hakairo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.hakairo.de/plugins-1/head-database.md).

# Head Database

## About

Through the head database, you can choose to purchase heads from selection of more than 25.000 custom heads, ranging from decoration, plants, food, alphabet blocks and more. It's a great option to enhance your builds and really get creative with.

## /hdb

/hdb opens the head database GUI. From there you can go into different categories of heads and browse through them. Buying heads is as simple as clicking on the head you want to buy. Heads cost 300$ per head.

![/hdb](/files/-MboImusgtYWkFwBM13u)

## /hdb search \[input]

With this command you can search for heads by name. Should you forget, clicking on the `compass` in the bottom right of the GUI will also input this into chat.


---

# 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://wiki.hakairo.de/plugins-1/head-database.md?ask=<question>&goal=<endgoal>
```

`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.