> 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/target/index/proxy-sdk.md).

# Proxy SDK

## Selecting the Connection Type

Once you have [selected your connection type](/ai-red-teaming/probe/target/add-target/integration-setup.md#selecting-a-connection-type), a configuration tab will appear on the next step, prompting you to input the required connection details.

## Integration Setup

<figure><img src="/files/obvgPVUE3G4mgsXXXUJC" alt=""><figcaption><p>Figure 1. Proxy SDK Connector</p></figcaption></figure>

* **URL** - This is your target endpoint to which the attack messages will be sent.
* **API Key** - The API Key for your application, used to ensure successful authentication with the Proxy SDK.
* **Additional POST Request Payload** - This section allows you to define custom payload data for POST requests sent by the Proxy SDK to the target. The payload is described as a JSON object.
* **HTTP Headers** - Custom HTTP headers are optional but may be required by the target for additional security, tracking, or configuration purposes.


---

# 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/ai-red-teaming/probe/target/index/proxy-sdk.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.