---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set up an AI proxy

# Set up an AI proxy {#ariaid-title1}

Release version: Australia  
Updated October 2, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure an AI proxy server to monitor AI commands traveling from your Agent Client Collector (ACC) agent to the AI Control Tower (AICT).

## Before you begin

* Install the ITOM Cloud Services Core (sn_itom_cloud_svc) plugin.
* Onboard your instance to use ITOM Cloud Services. For details, contact Customer Support.
* Configure an agent registration key. For details, see [Configure an agent registration key](https://www.servicenow.com/docs/LuF4oBp5jiWJiKWXZFwqmw "Configure an agent registration key so that you can deploy MID-less Agent Client Collector. Deploying MID-less Agent Client Collector enables you to use the MID Server for more persistent resources.").

You must configure ACC with an ICS (mid-less) architecture to enable using an AI proxy. For details on configuring ACC without a MID Server, see [Configuring MID-less Agent Client Collector](https://www.servicenow.com/docs/XzdpoJFIS~3grGL0dok96w "Configure MID-less Agent Client Collector to enable sending information through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.").

Role required: agent_client_collector_admin

## Procedure

1. Retrieve the publicly accessible gateway URL, based on your location.  
   * AMER (Americas): itomcnc-prod-gateway-amer.sncapps.service-now.com:443
   * EMEA (Europe): itomcnc-prod-gateway-emea.sncapps.service-now.com:443
   * APAC (Asia Pacific): itomcnc-prod-gateway-apac.sncapps.service-now.com:443
   {#ai-proxy-setup__ul_nlh_l5d_ndc}
2. Run the relevant command, depending on the OS you're using.  
   * On a Windows server:

         msiexec /i <msi_file_path> /quiet /qn /norestart CONNECT_WITHOUT_MID="true" ACC_CNC="<itom_gateway_url>" REGISTRATION_KEY="<agent_registration_key>" INSTANCE_URL="https://<instance_url> AI_PROXY_ENABLED="true" LOCALUSERNAME="LocalSystem" 

   * On a Linux or macOS server:

         sudo CONNECT_WITHOUT_MID="true" ACC_CNC=<itom gateway url> REGISTRATION_KEY=<agent registration key> INSTANCE_URL=<instance url> AI_PROXY_ENABLED="true" LOCALUSERNAME="LocalSystem" bash -c "$(curl -L https://<instance url>/api/sn_acc_shadow_ai/agents/install_agent)"

   {#ai-proxy-setup__ul_emn_4nr_tkc}

   For details on the parameter values in the command, see [Agent Client Collector MID-less installation command parameters](https://www.servicenow.com/docs/96PaoLSsRlU5J3gSfwBoWA "Description of the command line parameters used during MID-less Agent Client Collector installation.").

## Result

The AI proxy monitors AI traffic coming from your AI tools. Traffic is either allowed to pass through to the AI Control Tower, or is blocked, depending on your configured AICT policies.

## What to do next

Configure AICT policies to determine which AI resources are blocked, and for whom. For details, see .