> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/bug-bounty/bug-bounty-overview.md).

# Bug Bounty Overview

## What is Bug Bounty?

Aikido Bug Bounty is a feature that lets you create programs to submit vulnerability reports and automatically analyze them using AI pentest agents. Your team or an integration can submit reports describing potential vulnerabilities, and Aikido's agents validate each one, producing confirmed findings with severity, proof-of-concept data, and remediation guidance.

{% hint style="info" %}
Bug Bounty is currently in **closed beta**. Open the **Intercom chat** in the bottom-right corner of Aikido to request access.
{% endhint %}

Bug Bounty is built on the same engine that powers [Pentests](/pentests/aikido-pentest.md). While a regular pentest proactively scans your application for vulnerabilities, Bug Bounty is purpose-built for processing researcher-submitted reports. Every submitted report triggers an automated AI analysis that produces validated findings.

## Submitting reports

There are two ways to submit vulnerability reports to a Bug Bounty program:

**Via the Aikido UI**

Navigate to your program and submit a report directly from the dashboard. See [Validating a Bug Bounty Report](/bug-bounty/submitting-a-bug-bounty-report.md#submitting-a-report-via-the-ui) for details.

**Via the Public REST API**

Submit reports programmatically, enabling integration with external bug bounty platforms or custom researcher portals. See [Validating a Bug Bounty Report](/bug-bounty/submitting-a-bug-bounty-report.md#submit-via-api) for details.

## What happens after submission

Every submitted report triggers an automated AI analysis. Aikido's agents use the report description (and any attached files) as context to investigate the reported vulnerability against your pre-configured scope. The result is a set of validated findings, each with severity, attack type, CWE references, example request/response data, and remediation steps.

You can monitor the analysis in real time from the assessment detail page. See [Validating a Bug Bounty Report](/bug-bounty/submitting-a-bug-bounty-report.md#reviewing-the-results) for a full walkthrough.


---

# 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://help.aikido.dev/bug-bounty/bug-bounty-overview.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.