> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/tutorial/turn-assets-into-ai.md).

# Turn assets into AI

*Last updated: June 6, 2026*

Assets give Aissist the knowledge it uses in conversations.

Add domains, web pages, and documents to build a searchable knowledge base for your agent.

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

### How assets work

Aissist indexes the text in each asset.

When a user asks a question, Aissist searches that indexed content and uses the relevant results as response context.

You can also link assets to specific sub agents.

This keeps each workflow focused and improves accuracy.

If assets stay too broad, Aissist may retrieve unrelated context.

That extra noise can reduce answer accuracy.

Associate assets with the right [sub agents](/tutorial/create-sub-agents.md) whenever the content belongs to a specific workflow.

For example:

* link return policy assets to a return sub agent
* link order tracking content to an order tracking sub agent
* link billing documentation to a billing sub agent

### Supported asset types

Choose the asset type that fits your source:

{% content-ref url="/pages/G5FAL5NqZkcLqsnaAUlH" %}
[Website Domain](/tutorial/turn-assets-into-ai/website-domain.md)
{% endcontent-ref %}

{% content-ref url="/pages/GksAhaxUaodgbrV7Tivk" %}
[Web Page](/tutorial/turn-assets-into-ai/web-page.md)
{% endcontent-ref %}

{% content-ref url="/pages/XhfBIO0D0JhZ50cl1PTa" %}
[Google Drive](/tutorial/turn-assets-into-ai/google-drive.md)
{% endcontent-ref %}

{% content-ref url="/pages/eiBrP86QngvjhVab59cM" %}
[Documents](/tutorial/turn-assets-into-ai/documents.md)
{% endcontent-ref %}

### Test asset quality

Use the Asset Debugger to verify what Aissist can retrieve from your sources.

Then review the session detail page for live conversations.

For each AI reply, check the context used to generate the response.

If you see unrelated website or document content, narrow the asset scope by linking it to the correct sub agent.

{% content-ref url="/pages/ZAS8RVSKCZK4tK7UOpRA" %}
[Asset Debugger](/tutorial/turn-assets-into-ai/asset-debugger.md)
{% endcontent-ref %}

### Best practice

Start with your highest-value sources, such as help center content, policy pages, and operational documents.

Associate workflow-specific assets with the matching sub agents.

Then use the debugger to find gaps, conflicts, and outdated information before going live.


---

# 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:

```
GET https://doc.aissist.io/tutorial/turn-assets-into-ai.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.