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

# Species Compatibility

Species are defined as either a purebreds which will have a taxonomical classification, or defined as hybrid in which there will be no classification but instead a list of other species which the hybrid is based on. 

Purebreds have more and more compatibility with another species the further down the taxonomical classification they match on; Hybrid are only compatible with others of their own species (but this does not mean they can not be made compatible by the various options that are provided such as partnering, forced compatibility, breeding gardens)

<figure><img src="/files/gM4JOH2E1DjG8ziBpvwz" alt=""><figcaption><p>Kingdom</p></figcaption></figure>


---

# 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.anehud.com/getting-started/operation/species-compatibility.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.