> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/creating-assets/input-guidelines/input-image-examples/accessories.md).

# Accessories

For generating accessories we suggest:

* ‘High’ or ‘Ultra’ [generation quality](/creating-assets/prototype-assets.md#levels-of-quality) to capture all details
* Increasing poly count to at least 30-50K for increased detail
* Uploading more views/angles if available

## Suggested inputs:

### Multiple Views

It is always suggested to upload multiple views as separate images. The more angles, the better.

<figure><img src="/files/q87MJ846o70MrjHiE8uT" alt=""><figcaption></figcaption></figure>

### **Single view**

If uploading a single image, make sure the image shows most of the accessory ⬇️

<figure><img src="/files/FVK6s4HD0M2KRfDtd7zF" alt="" width="375"><figcaption></figcaption></figure>

## ❌Inputs to avoid

The input image should not be showing difficult or incomplete angles.

<figure><img src="/files/QZ9mTexHvzONl7riJgTt" alt="" width="270"><figcaption><p>In this image, the sunglasses are partially hidden.</p></figcaption></figure>

### Output Examples

<figure><img src="/files/8DJkP170tffO91Wc6KK3" alt="" width="188"><figcaption><p>Input image</p></figcaption></figure>

<div><figure><img src="/files/stH5kXkc65hSkq6z8iLc" alt=""><figcaption><p>27,312 tris / Standard quality</p></figcaption></figure> <figure><img src="/files/1edEKHBi3E5zjJCIHffP" alt=""><figcaption><p>92,080 tris / High quality</p></figcaption></figure></div>

{% hint style="info" %}
For more examples, see[ Generation Examples](/welcome/get-started/generation-examples.md)
{% endhint %}


---

# 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.kaedim3d.com/creating-assets/input-guidelines/input-image-examples/accessories.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.