> For the complete documentation index, see [llms.txt](https://info.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.kaedim3d.com/welcome/about-kaedim.md).
# About Kaedim
At [Kaedim](https://kaedim3d.com/), we combine state-of-the-art machine learning algorithms for 3D reconstruction with our in-house art team to generate production-ready 3D assets from images in a fraction of the time that traditional 3D modelling pipelines require.
By blending together our AI and artist-in-the-loop approach, Kaedim is able to provide a 10x speedup for companies that rely on 3D asset creation pipelines.
Today, Kaedim is supporting hundreds of game developers with their 3D content creation pipelines and teams at Fortune 100 companies across a variety of industries, including commerce, architecture, product design, and animation.
---
# 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://info.kaedim3d.com/welcome/about-kaedim.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.
