> For the complete documentation index, see [llms.txt](https://exobots.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://exobots.gitbook.io/docs/game-stages/beta/breeding-and-factory.md).
# Merge
Players are able to **Merge** their Exobots to create a new one. Even if it’s called ‘*Merge*’, the process is more like what we know as ‘*Breeding*’ in other games, meaning you won’t actually lose any Exobots you may want to use for this. Instead, each Exobot will have a **Merge Counter** that indicates how many times it is able to go through this process.
{% content-ref url="/pages/pApUqosfEOCfRXsYSYxv" %}
[How Merge works](/docs/game-stages/beta/breeding-and-factory/how-merge-works.md)
{% endcontent-ref %}
When two Exobots Merge, the new one will inherit parts and routines from the ascendants with a 50% probability to be from one or another. This means each part and routine will have the same chances to be inherited from either of the Ascendants.
Ultimately, to be able to use this Merge feature, players will need to purchase a ‘*Merging capsule*’ from the Marketplace with EXOS. Upon purchasing one, the *Merging capsule* will show up in-game for the player so they can add it to the Merging process along with the two chosen Exobots and finally creating a brand new one.
Some merge examples in-game
---
# 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://exobots.gitbook.io/docs/game-stages/beta/breeding-and-factory.md?ask=&goal=
```
`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.