Skip to main content
Agent Traffic shows requests to your site from recognized coding-agent user agents. Use it to find which documentation and product pages agents visit, then investigate those pages with Agent Experience evals.

​
Connect a source

Open Agent Traffic in Gauge Agents and choose a source. If Gauge finds an existing traffic source associated with your verified email, you can choose Connect existing source without changing its provider configuration.

​
Cloudflare

  1. Choose Cloudflare and select Authorize Cloudflare.
  2. Return to Gauge and choose the zones to monitor.
  3. Select Create Worker to deploy the traffic collection setup.
  4. Check the source status after requests reach your site.
The setup covers the selected zones and their subdomains without changing DNS.

​
Vercel

  1. Choose Vercel and save the endpoint URL and authorization header shown by Gauge. The secret is only displayed when created; rotate it if you lose it.
  2. In Vercel, open Team Settings → Drains and create a Custom HTTP drain for Logs. Your Vercel account must support this feature.
  3. Choose JSON or NDJSON, select Static Files, Functions, and Edge Functions, and enable Production.
  4. Use Gauge’s endpoint URL and the supplied Authorization: Bearer ... header value.
  5. Follow the verification step in Gauge and check that the source receives events.

​
Read the dashboard

Filter by time period, coding agent, host, or resource path. The dashboard shows recognized requests over time, requests by agent, requested resources, and recent request details. Open a resource to inspect its requests. Resource counts group canonical host and path pairs, with query strings removed. A request is not a unique user, a recommendation, or a successful integration. Identification depends on the request’s user-agent string, so traffic without a recognized identifier will not appear as recognized coding-agent traffic. A connected source with no recognized requests is different from a source that is not receiving logs.

​
Manage a connection

Use Rotate secret to replace a lost or exposed credential, and update your provider with the new value. Revoke stops the source from accepting new events; previously collected traffic remains available. If the dashboard is empty, check source status first, then widen the time range and clear filters. Confirm that your provider is sending production access logs and that requests with recognized coding-agent user agents have reached the site.