Updated: October 6, 2026 · Source-first reference130 documented agents & platforms · No paid rankings
AgentenCode evidence profileAutomation
✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Automation

Browser Use Agent

Browser Use Agent is classified by AgentenCode as a browser-agent api from Browser Use. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

Browser UseAutomationDevelopers & businesses
Automationeditorial classification
Browser Useprovider
10 primary sourcessource status
September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Browser Use Agent

Direct answer: AgentenCode currently documents 5 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.
Security contextSecurity & access3 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.
Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.
TraceabilityAudit & traceability0 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown
High confidence

API · Rest

Yes — documented

Browser Use provides a documented REST API for hosted agents.

Scope: browser_use_cloud_api_v4 · verified 2026-10-01 · Primary source ↗
High confidence

API · Webhooks

Yes — documented

Browser Use Cloud supports webhook delivery of agent events.

Scope: browser_use_cloud_events · verified 2026-10-01 · Primary source ↗
High confidence

Hosting · Managed

Yes — documented

Browser Use offers fully managed hosted agents and browser infrastructure.

Scope: browser_use_cloud_agents · verified 2026-10-01 · Primary source ↗
High confidence

Hosting · Self Hosted

Yes — documented

Browser Use's open-source agent can run on customer-managed local or server infrastructure.

Scope: browser_use_open_source_agent · verified 2026-10-01 · Primary source ↗
High confidence

Privacy · Data residency · Available

Yes — documented

Browser Use Enterprise offers an EU data-residency option for agents and browsers.

Scope: browser_use_enterprise_cloud · verified 2026-10-01 · Primary source ↗
High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Enterprise customers can request EU residency for Browser Use agents and browsers, providing a customer-selected regional residency option.

Scope: browser_use_enterprise_cloud · verified 2026-10-01 · Primary source ↗
High confidence

Protocols · Mcp · Server

Yes — documented

Browser Use exposes both hosted and local MCP servers.

Scope: browser_use_cloud_and_local_mcp · verified 2026-10-01 · Primary source ↗
High confidence

Security · Encryption · At rest

AES-256

Browser Use documents AES-256 encryption at rest.

Scope: browser_use_enterprise_cloud · verified 2026-10-01 · Primary source ↗
High confidence

Security · Encryption · In transit

TLS 1.2+

Browser Use documents HTTPS/TLS 1.2+ encryption in transit.

Scope: browser_use_enterprise_cloud · verified 2026-10-01 · Primary source ↗
High confidence

Security · Soc2 Type2

Yes — documented

Browser Use documents SOC 2 Type II compliance.

Scope: browser_use_cloud · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Browser Use Agent?

Browser Use Agent is classified by AgentenCode as a browser-agent api from Browser Use. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

Product-specific evidence for Browser Use Agent

This profile links 10 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Automatisierung.

Data Residency

Yes · Scope: browser_use_enterprise_cloud · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: browser_use_enterprise_cloud · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

AES-256 · Scope: browser_use_enterprise_cloud · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.2+ · Scope: browser_use_enterprise_cloud · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: browser_use_cloud · verified 2026-10-01.

Primary source ↗

protocols · mcp · server

Yes · Scope: browser_use_cloud_and_local_mcp · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

2primary sources
10field-level evidence claims
5documented trust controls
2history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Browser Use Agent is documented under Automation and is associated with Browser Use. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on September 30, 2026.

Trust coverage

5 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Browser Use Agent

Browser Use Agent is classified as Browser-Agent API from Browser Use. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Webdaten extrahieren

This use case is part of the stored profile for Browser Use Agent. The related strength is “API- und SDK-zentrierter Browser-Agent”. In a production evaluation, the practical boundary to verify is: Website-Nutzungsbedingungen und Automationsregeln beachten.

Browserbasierte Prozessautomation

This use case is part of the stored profile for Browser Use Agent. The related strength is “Cloud-Browser mit strukturierter Ausgabe”. In a production evaluation, the practical boundary to verify is: Login-Profile und Cookies besonders schützen.

Recherche über Webseiten

This use case is part of the stored profile for Browser Use Agent. The related strength is “Mehrstufige Web-Workflows”. In a production evaluation, the practical boundary to verify is: Fehlerfälle, Captchas und irreversible Aktionen abfangen.

Strukturierte Webaufgaben über API

This use case is part of the stored profile for Browser Use Agent. The related strength is “Profile, Sessions und Dateien integrierbar”. In a production evaluation, the practical boundary to verify is: Website-Nutzungsbedingungen und Automationsregeln beachten.

What to verify before adoption

  • Website-Nutzungsbedingungen und Automationsregeln beachten. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
  • Login-Profile und Cookies besonders schützen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
  • Fehlerfälle, Captchas und irreversible Aktionen abfangen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

  • September 30, 2026 · Verification Update
  • September 28, 2026 · Initial

Official sources

This profile links 10 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Browser Use Agent?

Browser Use Agent is listed by AgentenCode as an automation agent or agentic product from Browser Use.

How much trust evidence is documented for Browser Use Agent?

The current trust layer documents 5 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.