Connect any AI agent to your browser

1. What AI Bridge Gives Your Agent

AI Bridge runs a Chrome extension plus a small local server. Together they let an AI agent read a page, click and type, take screenshots, run JavaScript, and make authenticated calls to a site's own internal API using the session you're already logged into — without you copying tokens around by hand.

Everything runs on your machine. The only outbound calls are license validation and an optional Firebase token refresh — see the Privacy Policy for details.

2. Prerequisites

1. Install the AI Bridge Chrome extension and open the side panel.
2. Download the local bridge server — ai-bridge-bridge-macos-arm64.zip (macOS, Apple Silicon). It's a standalone binary — no Python install required. Unzip it, then run bash install_native_host.sh <EXTENSION_ID> once (extension ID is shown at chrome://extensions).
3. Click Start Bridge in the side panel — this launches the local server, no terminal needed after setup.
4. Activate your license key (get one at whop.com/ai-bridge) — required for tab control and Deep Capture.
5. Have a tab open in Chrome for the agent to act on.

Your agent shouldn't try to perform this setup itself — have it check GET /health first and ask you to confirm the bridge is running before it attempts anything else.

3. Connecting

Base URL: http://127.0.0.1:9124. Most routes require a shared-secret header, generated on first run and stored locally:

KEY=$(cat ~/.ai-bridge/key)
curl http://127.0.0.1:9124/health
curl -H "X-Bridge-Key: $KEY" http://127.0.0.1:9124/tokens

GET /health and GET /info need no key — always safe to probe first. A 401 means the key is missing or wrong; a 502 on a tab action means the extension isn't connected (check the side panel); an error mentioning the license means the key isn't active yet.

4. Endpoint Reference

No key required

Requires X-Bridge-Key

5. Example: Read, then Act

Don't guess selectors — read or screenshot the page first, then act:

curl -X POST http://127.0.0.1:9124/tab/screenshot -H "X-Bridge-Key: $KEY"

curl -X POST http://127.0.0.1:9124/tab/click -H "X-Bridge-Key: $KEY" \
  -d '{"selector":"[data-testid=save]","reason":"Save the draft"}'

Prefer calling a site's own API over clicking through its UI whenever one is available — it's faster and more reliable than DOM automation:

curl -X POST http://127.0.0.1:9124/proxy -H "X-Bridge-Key: $KEY" \
  -d '{"method":"GET","url":"https://example.com/api/v2/items","use_token":true}'

6. Best Practices

• Prefer /proxy over tab automation when the target site has an observable API for the action.
• Read before you click — selectors drift; confirm the element exists first.
• Don't hammer endpoints — a 429 means slow down, not retry immediately.
• Pass a reason on tab actions — it shows up in your confirmation prompt so you always know why the browser just moved.
• Deep Capture (raw network/WebSocket recording) is toggled from the side panel, not the API — turn it on only when you want an agent to see full request/response bodies.