AI agent trust guide

Should you block AI agents? Trust the person, not the agent.

AI agents are already on your site. Some read your pages so ChatGPT or Claude can answer a question. Some compare prices, check availability or fill in forms. Some add items to a cart. An agent is a middleman: its name proves nothing, anyone can pretend to be it, and the same agent can carry a loyal customer one minute and a fraudster the next. Decide on what it's trying to do, and who it's doing it for.

Definition

What is AI agent trust management?

AI agent trust management is how a business identifies the AI agents and bots reaching its website, decides what each one may do, and checks who is behind the request. It covers declared crawlers, signed agents, and automation that hides or impersonates, and it applies different rules to browsing, login, signup and checkout.

Meta's Muse made this urgent

But it's one agent among many, and new ones arrive every month. This guide covers all of them, with Muse as a worked example.

01 · What's on your site

What's on your site, and what proves it?

Not all AI traffic looks the same, and it doesn't all deserve the same answer. There are four kinds of AI bot traffic.

  • Declared

    Says what it is
    GET /products/hiking-boots
    User-Agent: Meta-ExternalAgent/1.1

    The bot says what it is in its user agent, like a search or AI crawler.

    Easy to see. Easy to copy.

  • Signed

    Web Bot Auth
    GET /products/hiking-boots
    Signature-Agent: [agent key directory]
    Signature: sig1=:[verified]:

    The agent signs its requests, so you can check cryptographically that it comes from who it claims.

    Proves the agent. Nothing more.

  • Undeclared

    Looks human
    GET /products/hiking-boots
    User-Agent: Mozilla/5.0 … Chrome/…
    (no signature)

    A normal browser, a normal user agent, no signature. Many of today's agents work this way.

    Invisible to a name check.

  • Impersonating

    Borrowed name
    POST /login
    User-Agent: ExampleAgent/1.0
    (claim, not proof)

    Traffic that claims to be an agent it isn't.

    The moment you allow an agent, it becomes worth dressing up as.

Kasada network

Small, but growing fast.

Across the sites Kasada protects, AI agent traffic is climbing fast, but it's still a small slice of the total. That's the point: set the rules while it's small.

AI agent traffic growth
~13x
March to September 2026
Share of all requests
~0.02%
Identified AI agents, October 2026
  • 1xMar 2026: 1x
  • ~13xSep 2026: ~13x
Identified AI agent requests per day across sites Kasada protects.Kasada network data, March to October 2026.

Verification

A name is a claim, not proof

robots.txt is a request, not a lock, and a user agent can be copied in a line of code. Signed agents are real progress, but a valid signature only tells you which agent it is.

  • Can robots.txt stop AI crawlers?

    Only if they listen
    # robots.txt
    User-agent: Meta-ExternalAgent
    Disallow: /search/
    # Read by crawlers that choose to listen.
    # Ignored by anything that doesn't.

    Well-behaved crawlers like Meta-ExternalAgent read it. Agents that act for a person, and anything that doesn't want to be stopped, often don't.

    A user agent is a suggestion, not an identity.

  • What Web Bot Auth proves

    And what it doesn't
    Signature-Agent: [agent key directory]
    Signature: sig1=:[verified]:
    # Which agent: answered
    # Who it's acting for: not answered

    A verified agent can still carry a stolen password, and one agent's reputation is shared by millions of people.

    Identity without authorization is just better labeling.

Verification answers one question out of three

  1. Q1

    Which agent is this?

    The signature answers it.

  2. Q2

    What should it be allowed to do?

    Your policy answers it. See the policy check below.

  3. Q3

    Who is it doing it for?

    The account behind it answers it.

02 · AI agent access control

The 30-minute policy check: decide by action, not by agent

Allow or block is the wrong unit. These are starting points, not recommendations: your rules depend on your customers, your risk appetite and what each agent brings you.

Where on your siteWhat's at riskA typical starting rule
Browsing, search, product and content pagesScraping, price harvesting, loadUsually allow, with limits
LoginCredential stuffing, account takeoverHold to a higher bar
SignupFake accounts, promo abuseHold to a higher bar
Checkout and paymentFraud, inventory abuse, chargebacksTest before you open it

Six questions, one journey at a time

Get Security and Marketing in the same room

You leave with a list of the agents you see and how each is verified, a rule for each step of the journey, an owner and a review date.

Run the check with our team
  1. What's already there?

    Which agents reach this journey, how much, and on which endpoints? Your analytics may undercount them, so check your bot-management or edge logs.

  2. What proves who it is?

    A user agent anyone can copy, an IP range that's hard to keep current, or a signed request? Rate each agent you see.

  3. What's pretending?

    How would you spot traffic claiming to be an agent it isn't, or an agent hiding as a person? A CAPTCHA won't settle it: an agent may solve it, fail it, or hand it back to the person.

  4. What may it do?

    For each step (browse, search, add to cart, log in, create an account, check out), decide what you'll allow.

  5. What does blocking cost?

    Ask Marketing which agents send real customers before you block them.

  6. How will you test and review?

    Allow one agent on one journey for a fixed window, keep checkout out of the first test, and agree the turn-off criteria in advance. Name an owner and a review date.

03 · Who's behind the agent

The agent tells you how someone got there. The account tells you who they are.

When an agent logs in, applies or buys, it usually acts inside a real person's account. That account already has a history. That's a record, not a guess. So that's where the decision belongs: verify the agent, then check the person behind it, and act on what you find.

  1. Request

    An agent logs in, applies or buys

    POST /login, via an AI agent.

  2. Step 1

    Verify the agent

    Which agent is this, and is it really that agent?

  3. Step 2

    Check the account behind it

    • Where it logs in from
    • What it buys
    • What it's connected to
  4. Act

    Act on what you find

    • Step up authentication
    • Hold the order
    • Stop the takeover

A stolen password looks different from its owner, even when both arrive through the same agent.

Same fraud, new route

Agents don't create new kinds of fraud so much as new routes for old ones.

AI agent fraud

Account takeover, fake accounts and checkout abuse can all arrive through an agent. The defense is the same as it's always been: know who you're really dealing with. The agent just makes it easier to forget to ask.

Account Intelligence

For customers using Account Intelligence, Kasada scores the person behind a request when they share identity, such as an email at login, signup and sometimes checkout, including when they arrive through an agent. We're working to extend this.

04 · Example

Should you block Meta Muse?

Muse is the agent everyone is asking about, so here's the framework applied to it.

What it is

Muse is Meta's AI agent. It browses, compares and shops for people from Meta's apps.

What proves it

Mostly nothing you can check easily. Most Muse traffic is unsigned, Meta doesn't publish an IP range, and requests arrive with a standard Chrome user agent from cloud machines. Meta has started signing a share of Muse requests with Web Bot Auth, and that may grow.

What blocking costs

Block it outright and you turn away real customers who chose to shop that way. Allow it on name alone and you let in everyone who uses it, and everyone who can pretend to be it.

Applying the check

Muse vs Meta-ExternalAgent at a glance

Browsing and product pages: usually fine to allow. Login, signup and checkout: a higher bar until you understand how your customers use it. Every step: check the account, not just the agent.

Read: Muse isn't the user. So who is?
CapabilityMeta-ExternalAgentMuse
RoleCrawlerActs for a person
Identifies itselfYesMostly no
User agentMeta-ExternalAgentStandard Chrome
Web Bot Auth—A share of requests, may grow

05 · For Marketing teams

What's really in your AI traffic?

Marketing teams are being told to get found by AI agents. Fair. But before you celebrate the AI traffic in your reports, ask what's in it: customers using agents to research and buy, or automation that looks like demand. Get it wrong and you fund the wrong campaigns.

Does GA4 show AI agent traffic? Partly. It can show visits referred from AI assistants. But an agent browsing for a person with a normal browser looks like an ordinary visit, and traffic that never runs your analytics script doesn't appear at all.

The best agent policies are written by Security and Marketing together. Go deeper with Forrester's best-practices report.

06 · How Kasada does it

How Kasada does it

Detects automation from the browser, not its name

It reads signals from the browser itself, not a user agent anyone can copy. No CAPTCHAs, so real people and the agents you allow never solve a puzzle.

Lets you set the rules

Allow, read-only or block each agent, or set rules by endpoint.

Grows the directory

We add new agents to the Verified Bots and AI Agent directory as they appear, starting with the most widely used.

Checks the account behind the agent

With Account Intelligence, when the person shares identity such as an email. We're extending this.

Recognized by analysts

Kasada is a Leader in The Forrester Wave™: Bot and Agent Trust Management, Q2 2026.

On-demand webinar

AI agent trust: what to allow, what to block, and what to prepare for

Our on-demand session on deciding what AI agents may do.

FAQ

AI bot traffic questions, answered

Not across the board. Blocking turns away customers who use agents; allowing on name alone lets in anyone who can pretend to be one. Decide per action: allow browsing, hold login, signup and checkout to a higher bar, and check the person behind the agent.

Start with robots.txt for crawlers that respect it, such as declared AI and search crawlers. For agents and automation that ignore it or hide their identity, you need bot detection that recognizes them from their behavior and browser signals, not their name.

Only the ones that choose to follow it. robots.txt is a request. Agents acting for a person, and anything trying to avoid detection, can ignore it.

It depends on what you publish and what you get back. Some businesses block training crawlers but allow AI search and answer crawlers that can send them visitors. Make it a deliberate decision per bot, and review it as new ones appear.

Not by its name. A user agent can be copied in a line of code. Detection has to look at the browser and the behavior behind each request, and separate signed agents, undeclared agents and impersonators. Kasada grades each agent by what it can prove and flags requests that claim an agent's name but fail verification. See AI Agent Trust.

Yes. Anything you allow becomes worth impersonating. That's why a name or user agent should never be enough to let something in.

Mostly no. Meta has started signing a share of Muse requests with Web Bot Auth, but most traffic is still unsigned, there's no published IP range, and it uses a standard Chrome user agent.

Not reliably. An agent might solve a CAPTCHA, fail it, or hand it back to the person halfway through checkout. Kasada doesn't use CAPTCHAs; it detects automation from signals in the browser.

Let agents do what helps customers, like browsing and comparing, and hold the steps that move money or accounts (login, signup, checkout) to a higher bar. Verify the agent, then check the person behind it.

Next steps

Security teams

Run the policy check with our team. Bring one journey; we'll work through the six questions with you.

Go deeper

Watch “AI agent trust: what to allow, what to block, and what to prepare for.”

Marketing teams

Forrester's best-practices report on telling trustworthy traffic from AI agents, bots and scrapers apart.

Defeats threats 
not your customers

Start deploying today