Connect your agent

Open Agents under the Red team category and choose Connect an agent. BotGauge asks how to reach your agent, then tests the connection right on the page. Nothing is attacked yet.

​

Choose how BotGauge reaches your agent

​

Connection details

These fields tell BotGauge how to send a message and read the reply. To save typing, choose Paste a cURL to fill this and BotGauge fills the form from your command.

​

Use a secret for credentials

Choose Use a secret next to the Value field to pick an existing project secret, or choose Add secret to create one. In headers, a secret is referenced by name, for example Bearer $ZENDESK_TOKEN. BotGauge passes only the reference to the runner, never the value.

​

Find your reply field

Call your agent once yourself and look at the JSON it returns. If the reply is at {"data": {"reply": "Hi!"}}, the reply field is data.reply.

​

Session handling (optional)

If your agent keeps a conversation going by returning an id, tell BotGauge where to find it. Session ID path is the location of the conversation id in your agent’s reply. For example, if the reply is { "data": { "session_id": "abc123", "reply": "Hi!" } }, the path is data.session_id. BotGauge reads the id from the first reply and sends it back with each following message, so your agent sees one continuous conversation. The connection test then checks that the conversation continues and that separate conversations stay isolated. Leave this empty if your agent doesn’t return a session id. BotGauge then treats each message on its own, and the test reports that there is no continuity.

​

Test the connection

Choose Test connection. BotGauge sends one test message and checks four things. Nothing is attacked, and the test takes about 10 seconds. If a check fails, the most common causes are these.

​

No agent handy?

Choose Use sample agent to try the sample refund agent. Its results don’t count. You can also open the sample agents already in your Agents list. See the red teaming quickstart.