> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/characters.md).
# Characters
Let's talk about the characters who you'll run into on Otherside
There are only 10,000 Kodas
## Kodas
Kodas are the main characters of Otherside.\
They use **Soma** to create forms and **Chaos** to take them away.\
If someone owns a Koda, they can play as that Koda.
In the Resource game, Kodas have special uses that gives players advantages.
## Voyagers
Kodas create Voyagers out of **Soma** or **Chaos**. They are the exoskeletons for these two forces, enabling them to move around and explore Otherside.
Soon, these Voyager exoskeletons will be upgraded to be customizable exoskeletons for Soma and Chaos.
## Custom Characters
In the world of Otherside, Kodas and Voyagers work together so that people can bring in their own characters and build their own worlds.
In this documentation, we'll sometimes refer to Custom Characters as Third Party Avatars (not created by Yuga Labs or one of its partners).
In the mainline Otherside experience, the use of custom characters must be unlocked.
In the ODK experiences, all custom characters are available to experience designers. While experience designers may place some limits, the core technology is designed for **maximum interoperability**.
---
# 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.otherside.xyz/odk-docs/characters.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.
