> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/knowledge/try-knowledge.md).

# Try Knowledge

Query a knowledge base, any version, and inspect the chunks behind each answer.

**Try Knowledge** lets you test a knowledge base before an agent uses it. Ask real user questions, inspect the retrieved chunks, and compare knowledge versions after a sync.

Open a knowledge base in **Console → Knowledge**, then select **Try Knowledge**.

{% hint style="info" %}
Try Knowledge answers from the selected knowledge version only. It does not use agent instructions, tools, or other knowledge.
{% endhint %}

### What you can do

{% columns %}
{% column %}

#### Test coverage

Ask questions your users will ask. A missing answer identifies content that needs syncing or improvement.
{% endcolumn %}

{% column %}

#### Verify retrieval

Inspect the chunks behind an answer. This shows whether the expected content was found and ranked well.
{% endcolumn %}
{% endcolumns %}

| Action                    | Use it to                                             |
| ------------------------- | ----------------------------------------------------- |
| Ask a question            | Check answer quality and knowledge coverage.          |
| View the execution report | Review retrieved chunks and citations.                |
| Select a version          | Compare the latest knowledge with an earlier version. |
| Refresh                   | Clear the conversation and begin a new test.          |

### Test a knowledge base

{% stepper %}
{% step %}

#### Ask a representative question

Enter a question and send it. Use the wording your users would use.
{% endstep %}

{% step %}

#### Review the answer

An answer based on missing context signals a coverage or sync issue.
{% endstep %}

{% step %}

#### Check the evidence

Open **Execution Report**, then select the answer's **Evaluation Report** to inspect its retrieved chunks.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Test questions that reflect real tasks. An agent using this knowledge base can only retrieve what the knowledge base contains.
{% endhint %}

### Inspect retrieved chunks

The execution report lists the chunks for the selected answer, most relevant first.

{% tabs %}
{% tab title="What each chunk shows" %}

* **Rank and title** identify the source section. A chunk can have no title.
* **Score** shows match strength from `0` to `1`. Higher scores indicate closer matches.
* **Tags** identify document attributes created during processing.

See [Document processing](/ai-workbench-qore/console/knowledge/document-processing.md) for processing details.
{% endtab %}

{% tab title="How to investigate an answer" %}

* If the expected section is absent, retrieval did not find it.
* If it ranks low, compare its tags and wording with the question.
* Check the source file and its processing before rewriting the question.
  {% endtab %}
  {% endtabs %}

### Compare knowledge versions

Select a version, then ask the same question. The selected version affects only this test. Agents always use the latest version.

| Compare                     | Check                                                  |
| --------------------------- | ------------------------------------------------------ |
| Latest and previous version | Whether the answer changed as expected.                |
| Retrieved chunks            | Whether the expected source is present and ranks well. |

See [Sync & versions](/ai-workbench-qore/console/knowledge/sync-and-versions.md) to learn how updates create knowledge versions.

{% hint style="warning" %}
Only synced content can answer questions. Files that are ready to sync or failed to sync do not contribute. Check file status in the **Datasets** tab when recently uploaded content is missing.
{% endhint %}

### Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Sync &#x26; versions</strong></td><td>Learn how file updates become knowledge versions.</td><td><a href="/ai-workbench-qore/console/knowledge/sync-and-versions.md">Sync &amp; versions</a></td></tr><tr><td><strong>Document processing</strong></td><td>Review the content, tags, extraction, and summary behind each document.</td><td><a href="/ai-workbench-qore/console/knowledge/document-processing.md">Document processing</a></td></tr><tr><td><strong>Attaching Knowledge to an Agent</strong></td><td>Give an agent access to a knowledge base.</td><td><a href="/ai-workbench-qore/console/agent-builder/build/attaching-knowledge-to-an-agent.md">Attaching Knowledge to an Agent</a></td></tr><tr><td><strong>Knowledge FAQs</strong></td><td>Get answers about knowledge bases, datasets, sync, and versions.</td><td><a href="/ai-workbench-qore/console/knowledge/faqs.md">Knowledge: FAQs &amp; Troubleshooting</a></td></tr></tbody></table>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/ai-workbench-qore/console/knowledge/try-knowledge.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.