> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/request-auditor-config.md).

# Configuring the Request Auditor

## Setting the LLM and model <a href="#request-auditor-llm-model" id="request-auditor-llm-model"></a>

For the [Request Auditor](/textual/tonic-textual-api/request-auditor.md), you can specify the LLM and model to use to review the sampled redaction requests.

If you do not configure a specific LLM and model for the **Request Auditor**, then Textual uses the LLM model set in `LLM_DEFAULT_PROVIDER` and `LLM_DEFAULT_MODEL_NAME`.

To configure the LLM provider for the **Request Auditor**, use the environment variable `REQUEST_AUDITOR_LLM_PROVIDER`. For the list of available providers, go to [Configuring the default LLM provider and model](/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/configuring-the-default-llm-provider-and-model.md).

To configure the model to use for the **Request Auditor**, use the environment variable `REQUEST_AUDITOR_LLM_MODEL_NAME`. For information about recommended models, go to [Configuring connections to LLM providers](/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/configuring-connections-to-llm-providers.md).

## Configuring request annotations and audits <a href="#request-auditor-annotations-audits" id="request-auditor-annotations-audits"></a>

To configure how Textual sends request content to the LLM and scores the results, set the following environment variables:

* `REQUEST_AUDITOR_ANNOTATION_CHUNK_SIZE_TARGET` - The target number of characters for content chunks. Used to split large request content before sending it to the LLM. The content is always split at the start of a new line. The default value is `5000`, meaning that Textual sends around 5000 characters at a time to the LLM.
* `REQUEST_AUDITOR_ANNOTATION_MAX_PARALLELISM`  - The maximum number of chunks to send to the LLM at the same time during NER annotation. The default value is `4`.
* `SOLAR_MAX_CONCURRENT_JOBS_AUDIT_REDACT_REQUEST` - The maximum number of concurrent request auditing jobs that the Textual worker can run. The audit compares the LLM results to the results from the original request. The default value is `8`.

## Scheduling the removal of expired requests <a href="#request-auditor-request-removal-schedule" id="request-auditor-request-removal-schedule"></a>

Textual runs a scheduled service to remove expired requests.

To configure the number of hours between runs of the service, set the environment variable         `PURGE_RECORDED_REDACT_REQUESTS_INTERVAL_HOURS`.

The default value is `1`, meaning that the service to remove expired requests runs every hour.


---

# 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.tonic.ai/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/request-auditor-config.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.
