> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/getting-started/generative-workflows-on-the-render-network.md).
# Generative Workflows on the Render Network
Guide to creating generative 3D art applications on the Render Network
ZenBlocks by MHX
Due to its parallelized computing architecture, the Render Network is a great tool for generative, code-based 3D workflows – enabling artists to concurrently render many generative permutations of a scene or 3D asset on thousands of high performance decentralized GPUs. \
\
With the [Render Network API](https://know.rendernetwork.com/getting-started/using-the-render-network-manager-app-and-render-network-api) and with [Differential Uploading](https://know.rendernetwork.com/getting-started/using-the-render-network-manager-app-and-render-network-api/differential-uploads-via-the-render-network-manager-app), artists also have powerful tools to programmatically manage their rendering workflows – from scripting uploads to managing outputs – allowing them to integrate compute intensive coding principals in their 3D workflows.
Alongside 3D rendering tools [Dispersed](https://dispersed.com/), the Render Network's new general purposed dockerized AI / ML compute platform, offers artists access to a customizeable and composable compute protocol for generative processing needs.
---
# 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://know.rendernetwork.com/getting-started/generative-workflows-on-the-render-network.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.
