Bot signals · AI crawler & agent

What is Inline AI crawler?

Requests from Inline AI crawler are known AI crawler or agent traffic: automated requests made by or for an AI product or service.

risk.is_airisk.is_crawler

Official documentation All AI crawlers & agents

01 · Profile

Inline AI crawler at a glance.

What to look for in your logs, and what the lookup API returns for its addresses.

Type: AI crawler & agent
API flag: risk.is_airisk.is_crawler

A user agent alone never sets a flag. Anyone can claim to be Inline AI crawler; the flag follows the address the request comes from.

02 · In the response

What a match looks like.

A lookup of a Inline AI crawler address sets risk.is_ai and risk.is_crawler. The flags come with geolocation and network data in the same response, for API keys on every paid plan.

This is AI crawling or retrieval traffic, so it counts as both AI traffic and crawler traffic.

The response says which kind of bot an address belongs to, not which operator. A request that claims to be Inline AI crawler while risk.is_ai is false should not be trusted as Inline AI crawler.

GET /api/lookup/{ip}?key=YOUR_API_KEY

{
  // … location and network fields …
  "risk": {
    "is_ai": true,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 · Control

Allow or block Inline AI crawler.

Your options

robots.txt works only for crawlers that choose to follow it. Check the operator’s documentation for the token it reads.
Firewall, WAF or CDN. Many offer bot rules you can allow or deny by category. Use them to enforce what robots.txt only asks for.
In your app. Look up the client address and allow or deny on risk.is_ai / risk.is_crawler, alongside the user agent.
Never on the user agent alone. Blocking the name stops only honest clients; allowing it lets anyone in who borrows it.