agent-traffic — скилл

---
name: agent-traffic
description: Classify HTTP traffic as agents, AI crawlers, search crawlers, bots or humans using the agent-traffic dataset. Use when adding agent or bot detection to request handlers, middleware, analytics, server logs or SQL queries, or when someone asks how much of their traffic comes from agents.
---

# Classify agent traffic

[agent-traffic](https://github.com/mintlify/agent-traffic) classifies HTTP requests as agents, AI crawlers, search crawlers, bots or humans. The dataset and rules are already written. Use them for whatever the user asks, whether that's classifying requests, analyzing logs or answering questions about their traffic, without changing what the rules mean.

## Sources

Read these before writing anything:

- [`GUIDELINES.md`](https://github.com/mintlify/agent-traffic/blob/main/GUIDELINES.md) has the categories, decision order and verification rules.
- [`data/agents.json`](https://github.com/mintlify/agent-traffic/blob/main/data/agents.json) lists known agents and crawlers: user agent patterns, `Accept` and `Signature-Agent` fingerprints, verification sources and real example user agents.
- [`data/http-clients.json`](https://github.com/mintlify/agent-traffic/blob/main/data/http-clients.json) lists generic HTTP libraries and headless browsers.

If the package is installed, the same data is at `node_modules/@mintlify/agent-traffic/dist/data/`. Every pattern is a case-insensitive regular expression.

## 1. Find out what's available

Before choosing an approach, look at the user's code or schema and confirm:

- **Where classification can run:** in request-handling code, in an ingest pipeline, or only over stored logs.
- **Which fields exist:** the user agent, the `Accept` header, other request headers, and the client IP. Also check whether that IP is the real client or a proxy or CDN address.
- **What they want out:** a single label, per-agent breakdowns, or verified-only numbers.

Every result needs at least the user agent. The `Accept` header and the real client IP make it much more accurate. If the user can add fields to their logs, recommend logging `Accept` and the real client IP.

## 2. Pick the approach

### JavaScript or TypeScript at request time

Install the package and call `classify` where requests are handled. Don't reimplement the rules.

```
npm i @mintlify/agent-traffic
```

```js
import { classify, loadIpRanges } from '@mintlify/agent-traffic'

let ipRanges

async function classifyRequest(request) {