> 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/updates/product-updates/march-2026/04.03.2026..md).

# 04.03.2026.

## Added Amazon Bedrock AgentCore Integration to the Platform

The Platform introduces integration with [Amazon Bedrock AgentCore](/ai-red-teaming/probe/target/index/amazon-bedrock-agentcore.md), providing users the ability to configure and manage associated targets with ease.

<figure><img src="/files/OrWW0gHryg5PP0ZMWXtt" alt=""><figcaption><p>Figure 1: Amazon Bedrock AgentCore Integration</p></figcaption></figure>

## Added AWS Bedrock Agents Integration to the Platform

With [AWS Bedrock Agents](/ai-red-teaming/probe/target/index/amazon-bedrock-agents.md) now integrated into Platform, users can effortlessly set up and oversee associated targets for a more streamlined experience.

<figure><img src="/files/iLX7jccejyh19SWzNvSP" alt=""><figcaption><p>Figure 2: AWS Bedrock Agents Integration</p></figcaption></figure>

## Added support for Responses API settings

A new **Response API type** for **Open API** **Targets** is introduced, allowing users to select between **Chat Completions API (default)** and **Responses API** on a per-Target basis.

This was introduced to support the newer **Responses API**, which is the forward-looking protocol and is better suited for modern reasoning/agentic workflows (including multi-tool calling and improved context handling). At the same time, **Chat Completions API** remains available as the default to preserve backward compatibility for existing integrations and deployments.

Target integrations affected:

* [**OpenAI Target**](https://docs.probe.splx.ai/ai-red-teaming/probe/target/index/openai)
* [**AzureOpenAI Target**](https://docs.probe.splx.ai/ai-red-teaming/probe/target/index/azure-openai)
* [**OpenAI Compatible Target**](https://docs.probe.splx.ai/ai-red-teaming/probe/target/index/openai-compatible-api)

## Probe Run: Rerun feature

A [**Rerun**](/ai-red-teaming/probe/probe-run/probe-run-view.md#rerun-probe-continue-probe-run) action is added for **Probe Runs** to make runs more resilient and easier to continue. The main purpose is to handle cases where something goes wrong during scanning (e.g., errors, interruptions) so you don’t have to restart from scratch-you can **continue from where the run stopped**, and optionally **retry attacks that ended in an error**.

<figure><img src="/files/EML5OTTFnnKYXrJfR4vh" alt=""><figcaption><p>Figure 3: Probe Rerun feature</p></figcaption></figure>


---

# 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.probe.splx.ai/updates/product-updates/march-2026/04.03.2026..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.