> 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/learn-more/concepts.md).

# Concepts

The Intangible-specific abstractions every other docs page assumes you know.

Read these once and the feature pages get a lot shorter. They explain how a project breaks into scenes and shots, why prompts get built from your scene, and what each action costs.

Intangible builds a project on the canvas from your prompt. Build, Compose and Visualize are the modes you open from a card to work by hand. See [The canvas](https://help.intangible.ai/canvas/canvas.md).

## Start here

* [Projects and scenes](https://help.intangible.ai/learn-more/concepts/projects-and-scenes.md): how a project is structured – scenes as locations, shots as time.
* [How Intangible works](https://help.intangible.ai/learn-more/concepts/how-intangible-works.md): the agents, the canvas, and the Build, Compose and Visualize modes you step into to take control.
* [How the visualizer thinks](https://help.intangible.ai/learn-more/concepts/how-the-visualizer-thinks.md): semantic 3D, and why prompts get built from the scene.

## Building blocks

* [Populators](https://help.intangible.ai/build/populators.md): the procedural environment generators – Houdini for normal people.
* [Image reference](https://help.intangible.ai/learn-more/concepts/image-reference.md): how a reference image attached to an object reaches the model.
* [Animation and shot time](https://help.intangible.ai/learn-more/concepts/animation-and-shot-time.md): why animation lives on the scene timeline, and each shot is a window into it.

## Cost

* [Credits and tokens](https://help.intangible.ai/learn-more/concepts/credits-and-tokens.md): what every action costs and where to see your balance.


---

# 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://help.intangible.ai/learn-more/concepts.md?ask=<question>&goal=<user_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.
