Run a red team campaign
Red teaming sends adversarial messages to your agent, such as prompt injections, requests for its hidden instructions, and attempts to trigger actions it shouldn’t take, then grades how it holds up. Try the hosted sample agent first, then connect your own agent with the CLI.
Only test agents you own or have permission to test. Prefer a non-production environment, and give the agent only the credentials and tools the test needs.
Start a campaign
Open the launchpad
Go to Red teaming and click Add agent. If your project has no campaigns yet, Red teaming opens the launchpad directly.
Try the sample agent
Next to Sample agent, click Run. It attacks a deliberately weak agent that Respan hosts, so you get a full report without any setup.
Connect your agent with the CLI
Next to CLI, click Set up. The CLI runs on your machine and relays the attacks to your agent, so your agent can stay private.

Install the CLI and sign in:
On a machine without a browser, click No browser? Use an API key to create an API key for the CLI.
Then ask your coding agent to write the adapter that connects the CLI to your agent:
Run the scan:
Leave the launchpad open. When the scan starts, the campaign opens by itself.
Watch it live
The campaign moves through Profile, Attack, Verify, and Report. Attacks, findings, and the score fill in as they land, and the score stays Preliminary until the report is ready.

Keep the CLI running until you see Report ready. If it stops early, the campaign is Paused: run the scan command again to continue.
Then review the report.
Write a good adapter
The setup file tells your coding agent what to build. Check these points before you scan:
- The adapter’s
labelis the agent’s name in Respan. Runs with the same label are grouped under one agent, and retests match findings by it, so keep it stable. open()starts a fresh conversation for each attack, andsend()takes one user message and returns the reply as a string.- Test it with one message:
Campaign allowance
Every campaign you start counts against your project’s allowance, including sample runs and CLI scans. Failed campaigns don’t count. The launchpad shows campaigns left, and Red teaming shows runs left. Hover the count to see your plan’s allowance and, on Team and above, when it resets. Team and above include 10 campaigns a month.
When none are left, click Upgrade, then View plans.
Run in CI
Store a Respan API key as the RESPAN_API_KEY secret, then run the scan with a grade threshold:
--output saves the report as JSON, and --fail-under B fails the job when the grade is below B.

