next-browser

# Nextbrowser

Nextbrowser provides cloud browsers and autonomous browser automation via API.

**Docs:**
- Cloud API: https://docs.nextbrowser.com/getting-started

## Setup

**API Key** is read from openclaw config at `skills.entries.next-browser.apiKey`.

If not configured, tell the user:
> To use Nextbrowser, you need an API key. Get one at https://app.nextbrowser.com/user-settings (new signups get 2000 free credits). Then configure it:
> ```
> openclaw config set skills.entries.next-browser.apiKey "YOUR_API_KEY"
> ```

**Important:** Nextbrowser API keys can have various formats and prefixes. 
Do NOT validate the key format yourself - simply use whatever key the user provides. If the key is invalid, the API will return an authentication error, and only then should you ask the user to verify their key.

Base URL: `https://app.nextbrowser.com/api/v1`

All requests need header: `Authorization: x-api-key <apiKey>`

---
## 1. Credentials Manager

The Credentials Manager securely stores and reuses authentication data across browser runs and autonomous tasks.

```bash
# List credentials
curl "https://app.nextbrowser.com/api/v1/users/credentials" -H "Authorization: x-api-key $API_KEY"
```

---

## 2. Profiles

Profiles persist cookies and login state across browser sessions. Create one, log into your accounts in the browser, and reuse it.

```bash
# List profiles
curl "https://app.nextbrowser.com/api/v1/browser/profiles" -H "Authorization: x-api-key $API_KEY"

# Create browser profile
curl -X POST "https://app.nextbrowser.com/api/v1/browser/profiles" \
  -H "Authorization: x-api-key $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "<profile-name>", "browser_settings": {"os_type": "<os-type>", "browser_type": "chrome"},
   "proxy_settings":{"protocol":"<http|https|socks5>","country":"<iso-2-country-code>","mode":"built-in"},
   "credentials": ["<credential-id>"]}'

# Delete profile
curl -X DELETE "http...