BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.

Browser Use

Point any model at a real browser and let it click, on a key and an endpoint you choose.

Website Source code

Category:
Automation Tools
Maintenance:
Actively developed (last commit yesterday)
Pricing:
Open Source
Open source:
Yes (MIT)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
CLI, Self-hosted, Local-only, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, OpenRouter, Ollama, Custom / OpenAI-compatible
API key storage:
Configured by environment variable
Key risk level:
LOW
Trust score:
87/100

Browser Use lets an AI agent drive a real browser, and is deliberately model-agnostic: you connect whichever provider you hold a key for, or a local model, rather than being tied to a vendor's hosted agent. It runs as a Python library on your own machine or server, so the browser session, the credentials it touches and the model choice are all yours. Worth thinking about before use: a browser agent acts with whatever access your browser profile has, which is a far broader blast radius than a chat tool. MIT, and the most-starred project in this directory.

Why this trust score (87/100)

Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.

  • Key Safety 22/25: The key is supplied by an environment variable or local config file you control.
  • Request Routing 17/20: Requests go straight from you to the AI provider.
  • Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled. Key handling was located in the published source.
  • Privacy 11/15: Local-first: it works without sending your data anywhere. Can be self-hosted, so the data path stays inside infrastructure you control. Analytics or error-reporting libraries are present; what they send was not established.
  • Maintenance 10/10: Actively developed, with commits within the last three months.
  • Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.

What was checked

Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.

  • [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
  • [STRONG · SOURCE_SCAN] The user supplies their own Anthropic key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
  • [STRONG · SOURCE_SCAN] The user supplies their own OpenAI key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own DeepSeek key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Azure OpenAI key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own xAI Grok key: the project references its API key variable. source
  • [CONFIRMED · SOURCE_SCAN] Ships a container definition, so it can be self-hosted on your own infrastructure. source
  • [REPORTED · SOURCE_SCAN] References PostHog, so some analytics or error reporting is present. This scan cannot tell whether it is opt-in or what it sends. source
  • [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-09-07, about 0 month(s) ago. source

How your API key is handled

Your API key is supplied via an environment variable or local config file. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.

Setup

Install the tool, set your provider API key as an environment variable (or in its config file), and pick a model.