> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/overview/faq.md). # FAQ Common questions, troubleshooting, and the honest list of what Intangible doesn't do today. The questions that come up often, and the things that don't quite work yet. * [Common questions](/overview/faq/common-questions.md): credits, plans, exports, AI behavior – the top-of-inbox set. * [Troubleshooting rendering](/overview/faq/troubleshooting-rendering.md): the wrong cop car keeps showing up; the model ignores my reference; the render is darker than the scene. * [Troubleshooting import](/overview/faq/troubleshooting-import.md): the model is in the ground; the model is the size of a building; the orientation is wrong. * [Known limitations](/overview/faq/known-limitations.md): video-to-video, USD bake-out, and the other things you'll notice are missing. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://help.intangible.ai/overview/faq.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 `build a script that syncs our docs to a CMS` 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.