Browserbase
Proxies the Browserbase REST API — sessions, contexts, extensions, and projects. Like ElevenLabs, it’s a whole API surface, so the gateway mounts a wildcard and forwards the path after /browserbase/ verbatim:
Because the path passes through unchanged, new Browserbase endpoints work without any gateway change. The methods are the REST verbs across sessions/contexts/extensions — GET, POST, PUT, DELETE.
Common paths
What the gateway injects and strips
- The
X-BB-API-Keyheader is injected, overwriting any client-supplied one. - The
Authorizationheader is stripped before forwarding — Browserbase has no use for your gateway token.
projectId is optional on session/context creation — Browserbase infers it from the API key — so the gateway injects nothing into the body. You may still pass projectId explicitly if you need to target a specific project.
WebSocket / browser automation
The WebSocket session is not proxied — the gateway is plain HTTP only.
Browserbase runs the actual browser automation over a WebSocket connectUrl that the session response returns. Create the session through the gateway, then connect your Playwright/Puppeteer client directly to the session-scoped connectUrl:
POST /browserbase/v1/sessionsthrough the gateway.- Connect your automation client directly to the
connectUrlit returns.
The master key still never reaches the client.
Example
The response is Browserbase’s JSON, returned unchanged. For request and response fields, follow Browserbase’s API reference — the gateway does not alter them.