CloudBrowser AI SOP

Appearance

Test ​

Status: NEEDS-ACCOUNT (paid) ​

Classification: NEEDS-ACCOUNT (paid cloud service) Install method: No SDK or local package. Use standard HTTP clients (curl, fetch) or Puppeteer/Playwright to connect to the returned WebSocket endpoint. Obtain the WebSocket URL via the REST API first. Cost tier: Paid only. No free tier. Requires account signup and an active subscription at cloudbrowser.ai. What is required: A paid CloudBrowser AI subscription and a valid API token (CLOUDBROWSER_API_TOKEN). No self-hosted option.

Smoke test: open a browser via the REST API ​

This test requires an active CloudBrowser AI subscription and your API token in the environment.

bash
curl -s -X POST https://production.cloudbrowser.ai/api/v1/Browser/Open \
  -H "Authorization: Bearer $CLOUDBROWSER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"headless": true, "keepOpen": 60}' | jq .

Expected success output ​

json
{
  "address": "wss://browserprovider-worker-<id>.cloudbrowser.ai/devtools/browser/<uuid>",
  "status": 200
}

The address field is the WebSocket DevTools endpoint you pass to puppeteer.connect({ browserWSEndpoint }). The hostname segment (browserprovider-worker-*) varies per session.

Failure outputs ​

json
{ "status": 401 }

Token is invalid or missing from the Authorization header.

json
{ "status": 402 }

No active subscription. Start a free trial or subscribe at https://cloudbrowser.ai/.

json
{ "status": 403 }

Browser-hour units are exhausted for this billing period.

json
{ "status": 404 }

The plan's concurrent browser limit is reached. Wait for an existing session to close or upgrade your plan.

Why this test was not run in-session ​

Running this smoke test requires:

  1. A paid CloudBrowser AI subscription (or active free trial account)
  2. A live CLOUDBROWSER_API_TOKEN environment variable
  3. Outbound HTTPS to production.cloudbrowser.ai

These preconditions are not available in the build environment. The curl command above is the definitive integration check. Run it from any shell with the token set to confirm the account and network path are functional before embedding CloudBrowser AI in an automation workflow.