
Anchor Browser
Documented identityAnchor Browser is listed here in the browser automation category and is associated with Anchor. Provides browser infrastructure that AI agents can use to interact with websites. This profile explains the identity and its documented scope so readers can distinguish it from a downloadable coding agent or a language model. It is an independent reference, not an operator endorsement.
What Anchor Browser does
This is a browser service rather than a downloadable foundation model. Cloudflare lists a signature-agent directory for its browser identity.
Anchor Browser user-agent identity
The request identifier recorded for this profile is Anchor Browser. A display name, an HTTP user-agent string and a robots.txt product token can differ. Confirm the control spelling in the linked operator guidance before writing a rule. A name in a request header alone is not authentication: another client can copy it.
Browser infrastructure for agent workflows
A managed browser gives an application or agent a way to load pages and perform a workflow. It is infrastructure rather than a foundation model. Sessions, tools and permissions depend on the operator service and the application using it. A browser visit alone does not reveal the complete task or prove that every requested action succeeded.
For an integration, verify the supported interface, authentication requirements and current billing terms in operator documentation. For a website owner, distinguish browser automation from passive indexing. Review request context and any documented identity evidence. A product capability should not be treated as permission to access private pages or perform an action on behalf of another person.
How to investigate a visit
Keep a representative log entry with the requested URL, timestamp, response code and source address. Compare it with current operator documentation and any published identity evidence. Use published IP ranges, DNS checks or request-signature verification only when the operator actually supports that method. This profile does not publish guessed address ranges or a universal allow rule.
Scope, costs and source limits
A recorded visit does not establish a model version, an API token price or a software license. These properties belong to separate products and agreements. The details below state the scope that was established for this identity; unconfirmed implementation information is identified as such. Any subscription, API or browser-service charge must be checked on the operator's current pricing pages.
Anchor Browser questions
Can I install this crawler as an agent?
This is a web-identity reference. An operator-managed crawler or fetcher is not automatically available as self-hosted software. If the operator offers a separate SDK, API or browser product, use that product's documented installation and access process rather than assuming the crawler name is an installable package.
Where should I verify the details?
Review the source documentation for Anchor Browser and the Anchor website. For related entries, browse the XPU Live agent and crawler directory. To compare inference services separately, visit the AI provider directory.
What it can do
- Provides browser infrastructure that AI agents can use to interact with websites.
- Request identity: Anchor Browser
- Source-linked operator reference
- Distinct category: Browser Automation
Where it fits
- Browser infrastructure for agent workflows
- Web traffic identification and log investigation
- Comparing crawler and assistant roles
Models & deployment
Model compatibility
Not a standalone model endpoint. A supported model list and model-specific prices do not follow from this web identity.
Where it runs
Operated through Anchor infrastructure or its managed services. This profile is not a self-hosted deployment recipe.
Cost model
No per-token tariff is assigned to this crawler identity. Operator services, if offered separately, have their own current access terms and pricing.
Limitations & scope
This is a browser service rather than a downloadable foundation model. Cloudflare lists a signature-agent directory for its browser identity. User-agent matching alone does not authenticate a request. Technical behavior not confirmed in the linked sources is not asserted here.