Starfort

The Guardrail Test screen sends the messages you enter to the Starfort Guard API as they are and shows the response with its HTTP status and X-Request-ID. Use it to see what verdicts come back before applying the guardrail to AI agents, or to diagnose connection problems.

Building a request

Compose the request in the left panel.

• Connect profile - The AIM Starfort connect profile to use. Only profiles you are granted are listed

• Messages - The messages to inspect, each with a role (system, user, assistant) and its content. Add message sends several messages at once; the response shows a result for each

• Samples - Clicking a button replaces the message with a sample

  Button	Expected verdict
  Mobile number (MASK)	MASK
  Email (MASK)	MASK
  Test number (PASS)	PASS

• More options - Expand to set additional request values

  Item	Description
  process_type	input by default. Starfort's personal data policy applies to input only
  x-trace-id	A trace value to tell calls apart; use it to find the call in Starfort's records
  opticon.session_id / user_id / tags	Information attached to the call record. Separate tags with commas

Click Inspect to send the request.

Response

The response appears in the right panel.

• HTTP status, X-Request-ID, latency - Give the X-Request-ID when contacting Starfort support
• Verdict - A PASS (green), MASK (orange) or BLOCK (red) badge with how to handle that verdict
• Original and processed_content - The original and the masked text side by side for each message
• Detections (detected_items) - The matched rule (rule_name), category and sequence (mask_word), the original (matched_text) and the description (alert_message)
• Mask mappings (mask_mappings) - The original (original_text) and what replaced it (masked_text)
• Request body / Response body (JSON) - The JSON actually exchanged. Expand to view

Errors

When no verdict comes back, the error code, Starfort's error.code, error.message and error.details are shown with the action to take.

HTTP status	Meaning	Action
400	Malformed request	Fix the request according to error.details
401	API key missing, wrong or disabled	Check the API key of the connect profile
403	Access restricted	Contact AIM Intelligence
422	The engine does not accept the request	Shorten the input or fix its format
5xx	The engine could not reach a verdict	Retry later; contact support if it persists

For connect-profile-level error codes (217400 to 217421), see the troubleshooting table in the Install Guide.