Skip to content
Agent Traffic Intelligence Early Access

Identify AI agents and know which to trust.

Kairal checks who an agent is, what it is trying to do and whether that activity belongs on your website. Give useful automation the access you choose.

Agent access
Requested page

/products/

Claimed identityIdentity checkDecision
OAI-SearchBot Verified
VERIFIED
ClaudeBot Verified
Blocked
OAI-SearchBot Unverified
Blocked

Know who’s visiting. Decide what they can do.

An agent reading your catalogue, collecting your articles or acting for a shopper needs different access. Kairal brings identity checks, purpose classification and access policies together so you can make those decisions in one place.

Agent identity verification

Check whether a request comes from the agent it claims to be. A familiar name in the user-agent header is a claim, not proof.

Purpose classification

Separate search, training and shopping assistants. Review what an agent declares alongside the pages it visits and the requests it makes.

Page-level access control

Choose which pages and actions each agent can access. Permission to read a product page does not grant permission to sign in or place an order.

Give each agent the right access.

Agent identity verification

Verify the identity behind the name.

An attacker can copy a recognised crawler’s name. Kairal checks the connection behind that claim and examines its requests, helping you distinguish genuine agents from impersonators.

Identity verification
Claimed nameOAI-SearchBotIP 192.0.2.10
Verified
Claimed nameOAI-SearchBotIP 198.51.100.24
Unverified

Same claimed name. Different verification result.

Purpose classification

Separate search, training and shopping assistants.

Search helps people find your pages. Training collects material for models. Shopping assistants retrieve information or act for a customer. Treat each purpose separately, and keep uncertain traffic under review.

Purpose and requests
Declared purposeObserved requests
Search
/products//categories/
Training
/articles/01/articles/02
Shopping assistant
/products/01/delivery/

A request sequence alone does not prove purpose.

Page-level access control

Set boundaries around what happens next.

Let an agent read public information while protecting account pages and checkout. Set access policies around the pages and actions you choose to make available.

Page access policies

Shopping assistant

/products/01
VERIFIED
/availability/
VERIFIED
/account/settings/
Blocked

Control agent access where it matters.

Product discovery

Give shopping assistants access to product details and availability. Review repeated catalogue collection separately from requests that support a customer’s purchase.

Articles and archives

Set different policies for search indexing and training collection. Keep decisions about how readers find your work separate from decisions about who can collect it.

Listings and seller information

Decide which listing pages agents can read. Apply separate controls to contact details, seller profiles and messaging.

Ticket availability

Distinguish requests for event information from repeated checks of seat availability. Keep booking and purchase actions under their own access rules.

Accounts and checkout

An identified agent still needs permission to act. Keep login, account changes and order submission subject to your authentication and purchase controls.

APIs

Define which endpoints agents can access and for what purpose. An agent’s identity does not replace the credentials or permissions your API requires.

See who comes back. Understand what they read.

Measure AI requests by company and purpose. Separate user-triggered visits, AI search and training collection, then follow how each changes over time. See which agents keep returning and which pages they read most.

AI traffic analytics

Why they come

10,196AI requests

Select a purpose to isolate its requests in the chart.

By company

OpenAI
3,800
Anthropic
2,000
Perplexity
375

Selected leading companies · total requests

AI requests per day

User-triggeredAI searchTraining
09
10
11
12
13
14
15
16
17
18
19
20
21
22

See the requests. Understand the decision.

Review the agent’s claimed identity, the IP, the pages requested and the response applied. Follow requests across a session to understand why traffic was let through or blocked.

Decision detail
Session · A-104
GET /products/01200
GET /availability/200
GET /account/settings/403
Selected request

/account/settings/

Claimed identity
ChatGPT-User
Verification
Verified
IP
192.0.2.30
Matched policy
No agent access to account settings
Blocked by policy
Why was it blocked?

The identity is verified, but the policy does not give this agent access to account settings.

Use that record to adjust access when a policy interrupts useful automation or leaves unwanted collection unchecked.

Put agent policies into place.

Start with the pages agents already visit and the actions you want to control. We’ll review your edge or server setup with you and agree where identity checks and access decisions belong.

Explore integrations

Go beyond the name in the request.

What you checkWhat it tells youWhat still needs checking
User-agent headerThe identity a request claimsWhether it genuinely comes from that agent
Verified identityEvidence of who sent the requestWhether the requested action is permitted
Declared purposeWhat the operator says the agent doesWhether its requests match that purpose
Pages and requestsWhat the agent accesses on your siteWhether that access fits your policy

Knowing who sent a request helps you assess it. It does not establish permission to access every page or act for a customer.

Built by people who understand automation.

Our founders built bots. Our team comes from offensive security, scraping and traffic analysis. We understand how automation is built, how it presents itself and how operators change it when access is blocked.

That experience shapes how we examine agent traffic: check the identity, follow the requests and assess whether the action belongs on your website.

About Kairal

Define the role of agents on your website.

Tell us which agents you want to welcome, which pages they should reach and which actions need tighter control.

Discuss agent accessAgent Traffic Intelligence is in early access.