> For the complete documentation index, see [llms.txt](https://docs.burpgpt.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.burpgpt.app/welcome.md).

# Welcome

This page provides an overview of BurpGPT Pro.

BurpGPT Pro brings AI-assisted analysis directly into Burp Suite Professional. It integrates with [supported model providers](/getting-started/supported-model-providers.md), including Anthropic, Google AI Gemini, Mistral AI, OpenAI, Ollama, and OpenAI-compatible APIs.

You can use the extension to analyse HTTP traffic with the AI scanner, manually send selected requests and responses for review, or ask follow-up questions from the `AI Chat` editor tab inside Burp's message editor.

The extension is designed for security testing workflows where model output supports, but does not replace, manual validation. AI-generated findings can be incomplete or inaccurate, so always verify results before reporting them.

{% hint style="info" %}
Third-party model-provider usage costs are not included. Cloud provider API accounts, keys, quotas, and billing are managed separately with the selected provider.
{% endhint %}

Start with [Quick start](/getting-started/quick-start.md) for the shortest path to a working setup, or go directly to [Installation](/getting-started/installation.md) if you are loading the extension for the first time.


---

# 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.burpgpt.app/welcome.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.