Agent Trust Manager: Quickstart Guide

What this is

A single script tag that lets you see how much AI agent traffic is already hitting your site. Add it to any page, and Arkose starts detecting and classifying agent activity on that page, with no backend integration, no code beyond the tag, and no action taken on your visitors.

Use it to answer one question before committing to a full integration: how many agents are on my pages today, and what kind?

What you get

• A clear picture of the AI agent traffic reaching the pages you tag, over the duration of the proof of concept
• A breakdown of which agents are visiting, how much of your traffic they represent, and how that changes over time
• Setup in minutes, on any page you choose, with no change to how your site works for visitors

What you need

Contact us to start a proof of concept. We will set up two things for you:

• Your public key - This identifies your site to Arkose and is part of the script tag below.
• Your custom domain - The Arkose script is served from a domain we configure for you

On your side, all you need is a page where you can add two lines of script.

Add the tag

Paste both lines into the <head> of the page. Keep them in this order: the callback must be defined before the script that calls it. Place them as early in the as you can, before your own scripts. The tag loads synchronously so it runs before the page becomes interactive — agents act quickly, and a script that loads late misses them.

<script>function atmDetect(a){a.setConfig({onReady:function(){a.run()},onCompleted:function(){}})}</script>

<script src="//<your-custom-domain>/v2/<PUBLIC_KEY>/api.js" data-callback="atmDetect" ></script>

Replace <your-custom-domain> and <PUBLIC_KEY> with the values we provide. Load the tag once per page.

If your site enforces a Content Security Policy, allow the Arkose domains first. See the Content Security Policy documentation.

That is the whole integration. The tag runs as the page loads, Arkose records and classifies the session automatically, and nothing is shown to or required from your visitors.

See your results

Once the tag is live, Arkose begins capturing and classifying sessions from that page immediately. Let it run long enough to collect a representative sample of your traffic, typically a few days, and we will share the results with you: which agents were seen, how often, and what share of the page's traffic they represent.

To see a detection land right away, load the tagged page using an AI-powered browser or assistant and let us know when you have done so.

Good to know

• The tag sees the pages it is on. Agents that call your APIs directly, without loading a tagged page, are not captured this way.
• This shows detection, not enforcement. Nothing here blocks, challenges, or slows any visitor. Allow, Monitor, and Block rules require the server-side integration.
• A single-page tag is a narrower view than a full integration. Results reflect what Arkose can observe on that page, not the full extent of what Agent Trust Manager detects across a complete session.

Loading asynchronously

By default the tag loads synchronously so that it executes before the page becomes interactive. If you prefer it not to block rendering, you can add the async attribute to the second script tag.

Be aware that an async script runs only when it gets a turn on the browser’s main thread, which on a busy page can be after an agent has already acted.

Sessions that complete before the script runs are not tagged, so your detection counts — and any latency you measure from the tag — will understate what Arkose would report with synchronous loading. See Latency best practices

Next Step

When you are ready to act on what you see, the full Agent Trust Manager integration adds the Verify API call and returns the agent_trust classification to your servers, so you can allow, monitor, or block agent traffic by policy.