Skip to main content

verdictan agent

The verdictan agent command group manages control-plane agent records and gateway bindings. These commands must use API authentication. Set VERDICTAN_API_TOKEN. Alternatively, sign in with verdictan auth login.

For read operations, you must have the matching agent list/read action. Mutations use the applicable create, update, delete, bind-gateway, or unbind-gateway action. An organization-wide write role does not make a missing resource ID correct.

List agents​

verdictan agent list
verdictan agent list --status active
verdictan agent list --json

list also accepts the standard connection, profile, and region overrides. If the compact table does not print the necessary fields, use --json. These fields include configuration, gateway, tag, and publication data.

Get one agent​

verdictan agent get --agent-id agent_abc123
verdictan agent get --agent-id agent_abc123 --json

Create an agent​

verdictan agent create --name "Customer Support Bot" --description "Handles tier-1 support queries"

Update an agent​

verdictan agent update --agent-id agent_abc123 --name "Customer Support Agent v2"

You can update the name, description, or status. The command fails when you supply no field.

Delete an agent​

verdictan agent delete --agent-id agent_abc123 --yes

You must use --yes. The delete command does not show an interactive prompt.

verdictan agent link-gateway --agent-id agent_abc123 --gateway-id gw_xyz
verdictan agent list --json

Make sure that the specified agent contains gw_xyz in gateway_ids. The API link operation is idempotent for a linked pair.

verdictan agent unlink-gateway --agent-id agent_abc123 --gateway-id gw_xyz --yes

The unlink command also must include --yes. The link command changes the control-plane binding. It does not start or install a gateway process on the local machine.

After you unlink the gateway, examine verdictan agent list --json again. Do not delete an agent to unlink the gateway.

Verification and troubleshooting​

verdictan auth whoami
verdictan agent get --agent-id agent_abc123 --json
verdictan agent list --json
  • 401 means the API token is missing, invalid, or expired.
  • 403 means the active identity does not have the applicable agent action.
  • 404 can mean that the ID is missing in the active organization or requested region.
  • If a binding succeeds but traffic does not run, only the control-plane state changed. Examine the gateway process and its selected agent independently.

Next steps​