Skill: Nextbrowser

Owner: highxshell

Summary: Use Nextbrowser cloud API to spin up cloud browsers for Openclaw to run autonomous browser tasks. Primary use is creating browser sessions with profiles (per...

Tags: latest:1.0.10

Version history:

v1.0.10 | 2026-02-19T09:49:04.414Z | user

• Added explicit instruction to not validate Nextbrowser API key formats; keys should be accepted as provided by the user.
• Updated API key setup instructions, including a generic placeholder and warning about possible formats.
• Clarified error handling: authentication errors should only prompt user action after a failed API response.
• No changes to file structure; content update only.

v1.0.9 | 2026-02-17T10:03:35.593Z | user

• Improved the Tasks endpoint documentation with details for polling task completion steps, including an example using from_step and explanation of new response fields.
• Clarified the meaning of status, steps, step_number, and total_steps in task polling.
• Added instructions on using optional query parameters when retrieving task status.
• No breaking changes to existing behavior or API usage.

v1.0.8 | 2026-02-17T08:47:32.641Z | user

Version 1.0.8 – No functional changes.

• No file changes detected; documentation and functionality remain the same as the previous version.

v1.0.7 | 2026-02-16T15:22:01.460Z | user

• Reordered sections: Credentials Manager is now listed before Profiles.
• Profiles endpoint updated—browser profile creation now supports a credentials field for associating credentials with a new profile.
• The subagent Tasks endpoint documentation was updated to remove credentials from example payloads.
• No code changes detected; this is a documentation update only.

v1.0.6 | 2026-02-12T10:51:07.565Z | user

• Added documentation for the Locations API endpoints, including how to list countries, regions, cities, and ISPs for configuring proxies and browser geolocation.
• Incremented Tasks (Subagent) section to section 4 to accommodate the new Locations section.
• No other significant changes.

v1.0.5 | 2026-02-04T14:34:35.724Z | user

• Added documentation for the new Credentials Manager feature, including usage example.
• Updated task automation example to demonstrate using credentials for login tasks.
• Expanded description to highlight new features: residential proxy, browser stealth, and CAPTCHA solving.
• Revised documentation for clarity and to reflect current task options and use cases.

v1.0.4 | 2026-02-04T10:42:42.446Z | user

• Renamed documentation file from SKILL.MD to SKILL.md to use correct filename casing.
• No changes to feature functionality or API usage.

v1.0.2 | 2026-02-04T09:19:04.937Z | user

• Fixed documentation of task status values: changed "completed" to "finished" and removed "stopped".
• Minor documentation improvements for accuracy and clarity.

v1.0.1 | 2026-02-04T08:15:59.439Z | user

• Minor update: Shortened example API response in the Tasks (Subagent) section for clarity.
• No other content or structural changes made.

v1.0.0 | 2026-02-03T16:41:24.729Z | user

• Initial release of Nextbrowser skill (v1.0.0)
• Supports creating and managing cloud browser profiles (with persisted cookies & logins) via API
• Enables running autonomous "task subagents" for browser automation using the fast mode
• API key configuration instructions included; requires Openclaw config entry
• Provides examples for profile management and running tasks, with links to official documentation

Archive index:

Archive v1.0.10: 2 files, 2955 bytes

Files: SKILL.md (7206b), _meta.json (132b)

File v1.0.10:SKILL.md

---

name: next-browser description: Use Nextbrowser cloud API to spin up cloud browsers for Openclaw to run autonomous browser tasks. Primary use is creating browser sessions with profiles (persisted logins/cookies) that Openclaw can control to manage social media and other online accounts. Secondary use is running task subagents for fast autonomous browser automation under residential proxy, browser stealth, and CAPTCHA solving capability. Docs at docs.nextbrowser.com.

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.

# 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.

# 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 "https://app.nextbrowser.com/api/v1/browser/profiles/<profile-id>" \
  -H "Authorization: x-api-key $API_KEY"

---

3. Locations

The Locations endpoints provide available geolocation metadata for proxy and browser configuration. Use them to dynamically discover supported countries, regions, cities, and ISPs before creating profiles or running tasks under specific network conditions.

# List Countries
curl "https://app.nextbrowser.com/api/v1/location/countries?\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<iso2-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List Regions
curl "https://app.nextbrowser.com/api/v1/location/regions?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<region-code>&\
city__code=<city-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List Cities
curl "https://app.nextbrowser.com/api/v1/location/cities?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<city-code>&\
region__code=<region-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List ISPs
curl "https://app.nextbrowser.com/api/v1/location/isps?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<isp-code>&\
region__code=<region-code>&\
city__code=<city-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

---

4. Tasks (Subagent)

Run autonomous browser tasks - like a subagent that handles browser interactions for you. Give it a prompt and it completes the task.

Always use fast mode - optimized for browser tasks, 3-5x faster than other models. Always use true for skip_plan_approval - optimized for automated tasks, skips the approval and improve performance.

curl -X POST "https://app.nextbrowser.com/api/v1/chat/tasks" \
  -H "Authorization: x-api-key $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "task_description": "'"\
Go to Reddit.com account, check if the account is logged in (if not, use credentials stored). \
Find 10 relevant posts on the topic of AI Agents, upvote 8 of them and post 3 witty-sounding comments \
that a cynical and funny Reddit user would post. Ensure that the comment is posted, ask for approval \
if you are not sure whether such comment is okay. By the end, you should have at least 10 relevant posts \
viewed, 8 upvotes, and 3 comments."\
"'",
    "mode": "fast",
    "profile_id": "<profile-id>",
    "skip_plan_approval": true
  }'

Endpoint: Poll for completion

curl "https://app.nextbrowser.com/api/v1/chat/tasks/<task-id>" \
  -H "Authorization: x-api-key $API_KEY"

curl "https://app.nextbrowser.com/api/v1/chat/tasks/<task-id>?from_step=3" \
  -H "Authorization: x-api-key $API_KEY"

• Query params (optional):
  • from_step: integer >= 1. First step index to return. Defaults to 1 if missing/invalid. Use this parameter to poll only new steps.

Response

{
  "success": true,
  "payload": {
    "status": "finished",
    "output": "Task completed. 10 relevant posts are viewed, 8 upvotes are done and 3 comments posted.",
    "isSuccess": true,
    "steps": [
      {
        "created_at": "2025-01-01T10:00:00Z",
        "finished_at": "2025-01-01T10:00:05Z",
        "description": "Opened Reddit search page",
        "status": "completed",
        "step_number": 1
      }
      // ... more steps starting from from_step
    ],
    "total_steps": 5
  },
  "errors": {},
  "description": "Task retrieved successfully"
}

Field semantics

• status: high-level task status: "processing" | "finished" | "failed".
• output: final task output (if available).
• isSuccess: true if task finished successfully, otherwise false.
• steps: list of task steps starting from from_step (or from 1 by default).
• step_number: sequential number of the step within the task, always starting at 1 in this array.
• total_steps: total number of steps the task has, independent of from_step.

Task options

| Option | Description | |--------|------------------------| | task_description | Your prompt (required) | | mode | Always use fast | | profile_id | Use a profile for auth | | skip_plan_approval | Always use true|

---

Full API Reference

See references/api.md for all endpoints including Sessions, Files, Skills, and Skills Marketplace.

File v1.0.10:_meta.json

{ "ownerId": "kn7a8m5059feezn28g9t7z6hrn80dw4s", "slug": "next-browser", "version": "1.0.10", "publishedAt": 1771494544414 }

Archive v1.0.9: 2 files, 2831 bytes

Files: SKILL.md (6918b), _meta.json (131b)

File v1.0.9:SKILL.md

---

name: next-browser description: Use Nextbrowser cloud API to spin up cloud browsers for Openclaw to run autonomous browser tasks. Primary use is creating browser sessions with profiles (persisted logins/cookies) that Openclaw can control to manage social media and other online accounts. Secondary use is running task subagents for fast autonomous browser automation under residential proxy, browser stealth, and CAPTCHA solving capability. Docs at docs.nextbrowser.com.

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 "nb_your_key_here"

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.

# 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.

# 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 "https://app.nextbrowser.com/api/v1/browser/profiles/<profile-id>" \
  -H "Authorization: x-api-key $API_KEY"

---

3. Locations

The Locations endpoints provide available geolocation metadata for proxy and browser configuration. Use them to dynamically discover supported countries, regions, cities, and ISPs before creating profiles or running tasks under specific network conditions.

# List Countries
curl "https://app.nextbrowser.com/api/v1/location/countries?\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<iso2-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List Regions
curl "https://app.nextbrowser.com/api/v1/location/regions?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<region-code>&\
city__code=<city-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List Cities
curl "https://app.nextbrowser.com/api/v1/location/cities?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<city-code>&\
region__code=<region-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

# List ISPs
curl "https://app.nextbrowser.com/api/v1/location/isps?\
country__code=<iso2-country>&\
limit=<limit>&\
offset=<offset>&\
name=<name>&\
code=<isp-code>&\
region__code=<region-code>&\
city__code=<city-code>&\
connection_type=<connection-type>" \
  -H "Authorization: x-api-key $API_KEY"

---

4. Tasks (Subagent)

Run autonomous browser tasks - like a subagent that handles browser interactions for you. Give it a prompt and it completes the task.

Always use fast mode - optimized for browser tasks, 3-5x faster than other models. Always use true for skip_plan_approval - optimized for automated tasks, skips the approval and improve performance.

curl -X POST "https://app.nextbrowser.com/api/v1/chat/tasks" \
  -H "Authorization: x-api-key $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "task_description": "'"\
Go to Reddit.com account, check if the account is logged in (if not, use credentials stored). \
Find 10 relevant posts on the topic of AI Agents, upvote 8 of them and post 3 witty-sounding comments \
that a cynical and funny Reddit user would post. Ensure that the comment is posted, ask for approval \
if you are not sure whether such comment is okay. By the end, you should have at least 10 relevant posts \
viewed, 8 upvotes, and 3 comments."\
"'",
    "mode": "fast",
    "profile_id": "<profile-id>",
    "skip_plan_approval": true
  }'

Endpoint: Poll for completion

curl "https://app.nextbrowser.com/api/v1/chat/tasks/<task-id>" \
  -H "Authorization: x-api-key $API_KEY"

curl "https://app.nextbrowser.com/api/v1/chat/tasks/<task-id>?from_step=3" \
  -H "Authorization: x-api-key $API_KEY"

• Query params (optional):
  • from_step: integer >= 1. First step index to return. Defaults to 1 if missing/invalid. Use this parameter to poll only new steps.

Response

{
  "success": true,
  "payload": {
    "status": "finished",
    "output": "Task completed. 10 relevant posts are viewed, 8 upvotes are done and 3 comments posted.",
    "isSuccess": true,
    "steps": [
      {
        "created_at": "2025-01-01T10:00:00Z",
        "finished_at": "2025-01-01T10:00:05Z",
        "description": "Opened Reddit search page",
        "status": "completed",
        "step_number": 1
      }
      // ... more steps starting from from_step
    ],
    "total_steps": 5
  },
  "errors": {},
  "description": "Task retrieved successfully"
}

Field semantics

• status: high-level task status: "processing" | "finished" | "failed".
• output: final task output (if available).
• isSuccess: true if task finished successfully, otherwise false.
• steps: list of task steps starting from from_step (or from 1 by default).
• step_number: sequential number of the step within the task, always starting at 1 in this array.
• total_steps: total number of steps the task has, independent of from_step.

Task options

| Option | Description | |--------|------------------------| | task_description | Your prompt (required) | | mode | Always use fast | | profile_id | Use a profile for auth | | skip_plan_approval | Always use true|

---

Full API Reference

See references/api.md for all endpoints including Sessions, Files, Skills, and Skills Marketplace.

File v1.0.9:_meta.json

{ "ownerId": "kn7a8m5059feezn28g9t7z6hrn80dw4s", "slug": "next-browser", "version": "1.0.9", "publishedAt": 1771322615593 }