> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/platform-ui-tour/live-interface.md).

# Live Interface

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-5706ef7d8cd444abcce02433ba6f349a39543c15%2F11cf5e3ff18bf314411e44724fc270d09df0fb70829b035e279ac96c94139192-image.png?alt=media" alt=""><figcaption></figcaption></figure>

This is your home for no code testing. It is a graphical user interface that allows you to view the file you've uploaded as well as see all of the extracted information including the raw API JSON response in one location. To make use of this feature, on the left side menu, Click on **Live Interface**. There are two approaches to use the Live Interface feature:

* **Add a document**, or
* Making use of the **Use my camera** feature

### Uploading A New Document

With the **Add a** **document** feature located at the bottom of the live Interface, you can upload the documents that you want to the Live Interface and this will appear below. To do this, click on the **Add a** **document button** and select on the image document you want. You can only upload one document at a time.

However, to make uploads faster, you can drag and drop an image document in the image frame.

### Making Use Of The Use My Camera Feature

With the **Use my camera** feature located at the bottom of the live Interface, you can take pictures of your documents. You'll need to allow your browser or web cam to use your camera, otherwise, you won't be able to take a picture of your document.

### Extracted Fields

You can click on each of the files below to view the extracted fields for each document you have uploaded. Once your document is shown on the live interface, it automatically extracts fields from the document and highlights them. There are two different formats in which the results are shown:

* Expected fields
* API response fields

#### Extracted data

You can examine the extracted fields using the **Extracted data** column. This is a subset of what the API will return.

For products with the bounding boxes you can:

* Click on a field to have a focus on its position on the document.
* Or click on the bounding box to have the **Extracted data** list focus on the corresponding field.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-6f33b5e1eab886866f8bda76b7207b1a9b668f6d%2F8a451d6-expected-field.png?alt=media" alt="Expected fields column with extracted fields" width="563"><figcaption></figcaption></figure>

#### API Response

The API response gives a raw JSON of the extracted fields. It is the same response you will get from using the API in your application. There is more detailed information about the extracted data here than in the expected fields. You can easily download it with the arrow button at the top

You will see as well the response time of the API.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-36ba58e9242530980ecaefe666e4f43c3575f3c2%2F193f61cfe1e8500390e7d8e3382ab66c4fdcd501075fbe72e15d98402350ee0d-image.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
You can easily download the JSON with the arrow button at the top
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mindee.com/v1/platform-ui-tour/live-interface.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.
