> For the complete documentation index, see [llms.txt](https://docs.atlas.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atlas.design/atlas-ai-studio-overview/node-index.md).

# Node Index

Complete reference for every node available in Atlas workflows. Covers input, image, mesh, video, audio, API, and utility nodes with use cases, examples, and best practices for production-grade 3D con

Atlas workflows are built from nodes. Each node is a discrete capability: a model that generates content, a transform that processes it, a utility that routes data, or an API surface that exposes the workflow to external tools. Connect nodes together and you get a reusable production pipeline.

This index covers every node category on the Atlas platform. Use it as a reference when you're building or troubleshooting a workflow, or as a starting point for understanding what's possible. Each subsection includes node descriptions, use cases, common pitfalls, and frequently asked questions.

## Node categories

* **Input Nodes** — bring text, images, references, PDFs, and other source content into a workflow
* **Image Nodes** — generate, edit, and post-process 2D images at production quality
* **Mesh Nodes** — generate, refine, optimize, and prepare 3D meshes for game engines
* **Video Nodes** — generate and edit short video content from prompts and references
* **Audio Nodes** — synthesize speech, music, and sound effects from text or other inputs
* **API Nodes** — export workflows as callable REST endpoints for Unity, Unreal, Blender, or any backend
* **Utility Nodes** — orchestrate data, manipulate arrays, run LLM operations, structure outputs

{% content-ref url="/pages/z5pWvVdsIs9yrkRBnYBA" %}
[Input Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/input-nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/b4tN1RB4hbAu9ngELKqI" %}
[Image Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/image-nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/X47xyoIuTIP5yF2M7p8D" %}
[Mesh Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/mesh-nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/MRJmZU0Oi1Apux53AqG6" %}
[Video Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/video-nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/GfrKAa6nxmtPP6BDC8mn" %}
[API Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/api-nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/5TBpdTmEC1N31vwUvij7" %}
[Utility Nodes](https://docs.atlas.design/atlas-ai-studio-overview/node-index/utility-nodes.md)
{% endcontent-ref %}

Every node also has a credit cost per run. [Node Prices](https://docs.atlas.design/atlas-ai-studio-overview/node-index/node-prices.md) lists all of them by category, along with the settings that move each price.

{% content-ref url="/pages/J1AoCszgtf8s35bQomcO" %}
[Node Prices](https://docs.atlas.design/atlas-ai-studio-overview/node-index/node-prices.md)
{% endcontent-ref %}


---

# 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.atlas.design/atlas-ai-studio-overview/node-index.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.
