# Usage

As said in the [Configuration](/2.1.0/blurit-on-premise/installation/configuration.md) section, BlurIt OP Web Manager or API works within the paths set in `LOCAL_STORAGE_INPUT_PATH` and `LOCAL_STORAGE_OUTPUT_PATH`. Every processed media will be stored in `LOCAL_STORAGE_OUTPUT_PATH`, while the original media will be processed from `LOCAL_STORAGE_INPUT_PATH`.

There are two ways to process files with BlurIt OP:

1. Manager Webapp: The web app manager provides a Graphical User Interface (GUI) accessible at `http://<host> or https://<host>`, where "host" refers to the IP address of the machine where BlurIt OP is deployed or the dns url configured. This interface allows non-developers to process files easily.
2. API: The API is accessible at `http://<host>/api or https://<host>/api`. It allows developers to integrate BlurIt OP file processing capabilities into their own applications or workflows programmatically. This allows for greater flexibility and automation.


---

# Agent Instructions: 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-op.blurit.io/2.1.0/blurit-on-premise/usage.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.