> For the complete documentation index, see [llms.txt](https://faloker.gitbook.io/purify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faloker.gitbook.io/purify/master.md).

# Introduction

![](/files/-MHm8LmWQbpkjF-8jUJx)

## Description

The goal of Purify to be an easy-in-use and efficient tool to simplify a workflow of managing vulnerabilities delivered from various (even customs) tools.

Purify is aims to be a tool-agnostic application. Tool independence makes it possible to analyze reports of **any tool**. Technically, the report you want to upload should be one of the following:

* JSON file
* XML file
* JSON object (most webhooks dispatch events as separate JSON objects)

This means **you don't need any special plug-ins** to parse incoming reports. For this Purify introduces the concept of templates. Templates are code-free and user-friendly structures that parse reports the way you tell them.

Purify is able to remove duplicate results among various vulnerability scanners or tools. In addition, it can combine several results of the same tool based on some fields and it is fully configurable. Purify does all this work to reduce the headache of the analyst.

Collect all your findings in one place, review/validate/track them, collaborate with your teammates, receive notifications via Slack, create Jira tickets and many more.

## About this document

This documentation is dedicated for somebody who are going to use Purify.

{% hint style="warning" %}
In the rest of the documentation, all HTTP requests in snippets are performed using [httpie](https://httpie.org/).
{% 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 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://faloker.gitbook.io/purify/master.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.