Test a connected agent
Configure an HTTP target, run a bounded assessment, and inspect the evidence.
Two kinds of test
Direct evaluation checks text submitted to Nyraxis. Connected-agent testing calls your configured agent endpoint and records how that target responds to probes. Use the second path when you want to test the agent's actual model, tools, prompts, and runtime guards together.
Use an owned development target and synthetic records. A scan can invoke the target repeatedly and consume model or tool resources. Set a bounded probe scope and avoid tools with uncontrolled side effects.
Connect the target
Open Agents, select the agent, and open Connection. Choose a preset or configure the request manually:
| Setting | Purpose |
|---|---|
| Endpoint URL | The target's chat/request endpoint. |
| Connection mode | Stateless, session-based, or conversation ID, according to your target's contract. |
| Authentication | The target's own authorization method; separate from the Nyraxis ingest key. |
| Body template | Maps test input into the target's request body. |
| Response path | Extracts the text response from the target's JSON. |
A stateless body template for a target accepting an input string is:
{"input": "replace-with-test-input"}In the connection editor, replace that value with the editor's {{input}} placeholder without JSON quotes: {"input": {{input}}}. Template substitution JSON-encodes the input. For a JSON response {"output":"reply"}, set the response path to output.
Run the connection test. Confirm the target is reachable from the worker network, not only from your browser. Private-network and loopback access is deployment-controlled; the local QA fixture's network allowance is not a general cloud feature.
Run an assessment
Open Security → Red Team, select the connected agent, choose an assessment mode and bounded probe configuration, then submit. A queue receipt means the job was accepted, not that the target passed.
Inspect queued, running, completed, failed, cancelled, or incomplete states. A failed target call or unavailable judge must not be interpreted as a safe response. Some strategies use model-backed generation or judging and require separate configured provider access.
Read findings
Review the target, probe, response evidence available under capture policy, severity, and assessment scope. Counts describe the probes run in that assessment. A safe-response rate is not a general security score, and an interrupted run can contain only partial evidence.
Save an accepted finding as an agent regression, make a change, and rerun it. The regression guide explains assertions and CI.
Share evidence
Use the scan history and available report download. Verify the compared target/probe configuration, policy versions, incomplete checks, and retained content before sharing. Synthetic fixture results demonstrate that fixture; they are not a certification of another agent or production deployment.