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

# Probe

**Probe** is the adversarial testing module of the Platform. It allows you to proactively evaluate your AI systems against real-world, domain-specific attack patterns. With Probe, you can configure, execute, and analyze simulated adversarial runs to discover vulnerabilities. Figure 1 displays the **Probe Overview** page.

<figure><img src="https://1029475228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi12bk7lo75SODuwcRCQp%2Fuploads%2FRnIxv91oyLwrfVvHQqtL%2F2_overview_cards.png?alt=media&amp;token=40fc1b5b-190c-4f8f-8d96-625e5b28eaaa" alt=""><figcaption><p>Figure 1: Probe Overview Page</p></figcaption></figure>

{% hint style="info" %}

* Go to [**Getting Started**](https://docs.probe.splx.ai/ai-red-teaming/getting-started.md) for a step-by-step introduction to the AI Red Teaming module of Platform,  it guides you through running your first Test Run and filling the Probe Overview page with data.
* Go to [**Probe Overview**](https://docs.probe.splx.ai/ai-red-teaming/probe/overview-page.md) to get a better understanding about all the sections displayed on the **Probe Overview** page once they are populated with data.
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.probe.splx.ai/ai-red-teaming/probe.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.
