> For the complete documentation index, see [llms.txt](https://docs.boostfordaz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.boostfordaz.com/getting-started-101/does-boost-for-daz-work-with-3rd-party-content-assets.md).

# Does Boost for Daz work with 3rd party content/assets?

In our context, 3rd party assets are defined as assets or content that you download or purchase from some other site -  other that the Daz store.  &#x20;

The general rule of thumb working with 3rd party art from a Daz and Boost for Daz compatibility perspective is that **if your local Daz and local Iray CPU and/or GPU can see/use that 3rd party content then the same would be possible with Boost.** Essentially, by entering the Boost for Daz credentials into Daz Studio, you simply tell Daz to *not* use your local CPU/GPU resources, but instead transmit to a remote GPU on Boost for Daz.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.boostfordaz.com/getting-started-101/does-boost-for-daz-work-with-3rd-party-content-assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
