---
title: "Anchor Browser: user agent, token, block rate | Agent Ready Crawlers"
description: "Anchor Browser from Anchor: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published. Read 2026-11-04."
canonical: https://agentreadycrawlers.com/crawlers/anchor-browser
site: "Agent Ready Crawlers"
last_updated: 2026-11-04
section: "Crawlers"
---

# Anchor Browser: user agent, token, block rate | Agent Ready Crawlers

> Anchor Browser from Anchor: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published. Read 2026-11-04.

Source: https://agentreadycrawlers.com/crawlers/anchor-browser
Site: Agent Ready Crawlers
Last reviewed: 2026-11-04

Browsing agent from Anchor

# Anchor Browser

In short

Anchor Browser is Anchor's browsing agent. Anchor Browser has no robots.txt token, so robots.txt cannot address it and the crawl cannot measure a block rate. It signs requests with Web Bot Auth, so a signature can be checked. Anchor Browser has no operator bot documentation, checked 2026-11-04. Verisoul reports sessions can also be configured to pass as human.

Operator

Anchor Vendor profile: [Anchor Browser](https://agentreadycrawlers.com/vendors/anchor/)

Purpose

Task agent [All task agent rows](https://agentreadycrawlers.com/crawlers/purpose/task-agent/). A browsing agent that clicks, fills forms and finishes a job for a person.

User-agent string

No exact string is published. What the operator or a third party says: Can sign with Web Bot Auth depending on customer setup

robots.txt token

None. No robots.txt line can address this agent.

Respects robots.txt

No documentation

operator publishes no bot documentation (checked 2026-11-04) on robots.txt. [Source](https://blog.cloudflare.com/signed-agents/), read 2026-11-04.

Operator publishes no bot documentation (checked 2026-11-04).

Verification

Web Bot Auth signature

Requests carry an HTTP message signature that can be checked against the operator's published key directory. [Documentation](https://blog.cloudflare.com/signed-agents/), read 2026-11-04.

IP ranges

Not published.

Rate behaviour

Set by the customer.

Block rate

None: the agent has no token, so a robots.txt block rate does not exist.

Documentation

Operator publishes no bot documentation (checked 2026-11-04). [Closest page read](https://www.verisoul.ai/agents/anchor-browser).

Note. In Cloudflare's first signed-agents cohort. Verisoul reports sessions can also be configured to pass as human.

## Allow and refuse lines

This agent has no robots.txt token, so there are no lines to copy. Verify its signature in your WAF or edge rules instead, then allow or refuse the verified identity.

Refusing or allowing in robots.txt states a preference. For this row the operator or its documentation says robots.txt may not govern the fetch, so enforcement belongs in your WAF.

## Anchor in the Verification Ledger

Signing depends on customer configuration. [All operators](https://agentreadycrawlers.com/verification/).

IP lists

publishes nothing

Reverse DNS

publishes nothing

Key directory

signs per customer setup

Cloudflare

Cloudflare signed agent (cohort of 2025-08-28)

Visa TAP registry

no public operator-level registration found (checked 2026-11-04)

Mastercard Agent Pay

no public operator-level registration found (checked 2026-11-04)

## Sources

-   [verisoul.ai: anchor browser](https://www.verisoul.ai/agents/anchor-browser) read 2026-11-04
-   [The age of agents: cryptographically recognizing agent traffic](https://blog.cloudflare.com/signed-agents/) read 2026-11-04

Last reviewed 2026-11-04