x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
Skill by browser-use
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/browser-use-x402
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: backend, testing, writing, finance, browser-automation, payments-billing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/x402
Tools it pre-approves 4
From allowed-tools in SKILL.md: the agent may use these without asking you each time.
Bash,Read,Write,Edit
What's inside
- Skill name
x402- Description
- Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
- License
- MIT
- Allowed tools
- Bash,, Read,, Write,, Edit
- Instructions
- 327 lines in SKILL.md · view on GitHub
Before installing
- Pre-approves some shell commands
- Instructions call the network
Files (1)
- SKILL.md
SKILL.md (first lines)
# Browser Use Cloud — pay with x402 (crypto wallet)
This is a scripted flow. Follow the steps in order. x402 only works through the **SDK** (`browser-use-sdk` for Python, the `browser-use` npm package for TS) — there is no `browser-use` CLI command for it, so every step runs a short SDK script.
## How to use this script
- Lines under **Say:** are spoken to the user **word for word.** Don't paraphrase, add, or drop anything.
- `<like this>` inside a Say block is a fill-in — replace it with the real value, keep the rest exact.
- Lines under **Ask:** use the AskUserQuestion tool. Use the question and option text exactly as written.
- **To show an explanation before a question, put it inside the AskUserQuestion `question` field** (it renders above the options). Don't send it as separate chat text before calling the tool — that text gets dropped when the question UI opens. So: explanation + the actual question both go in the `question` field, in one tool call.
- Lines under **Do:** are your actions. Don't read them out.
- Track two facts as you go: `SETUP` (A or B, from Step 1) and `MODE` (A or B, from Step 2).
- **`SETUP`, `MODE`, and the Path A/B/C names are internal labels for you only. Never say them to the user.** Describe choices in plain words instead (e.g. "top up your account" / "accountless wallet"), never "Mode B" or "Path A".
---
## Step 1 — Open and pick the setup
**Ask:** (header: `Use x402`) — put the explanation and the question both in the `question` field, exactly:
> x402 is a protocol from Coinbase that, instead of presenting an API key, allows you to use crypto to pay for API requests. x402 lets you pay Browser Use per request from a crypto wallet with USDC on Base — no signup, API key, or credit card needed, just a wallet. Setup takes a few minutes: get or make a wallet, add funds, save the key in `.env`, and test it.
>
> How do you want to use x402?
- **Just use it** — Run Browser Use tasks, paid from your wallet, here in terminal by asking me. I set up the wallet and key.
- **Build it in** — You're coding an app and want x402 in it. I will help you install the SDK, save the key to your project's `.env`, and add code.
**Do:** "Just use it" → `SETUP = A`. "Build it in" → `SETUP = B`.
---
## Step 2 — Find the account (check before asking)
**Do:** Look for an existing Browser Use API key, in this order. Don't say anything yet.
1. `BROWSER_USE_API_KEY` in the environment
2. a `BROWSER_USE_API_KEY=` line in `./.env`
3. `~/.browser-use/config.json` (saved by `browser-use cloud login` / `signup`)
4. `browser-use doctor` output, if the CLI is installed
**If no key is found anywhere:**
**Say:**
> No Browser Use key found, so I'll set this up accountless: the wallet is your identity, and the first payment makes a project named after it.
**Do:** `MODE = A`. Go to Step 3.
**If a key is found:**
**Ask:** (header: `Account`) — question: `I found a Browser Use API key in <location>. Where should the USDC credits go?`
- **Top up that account** — Credits go to your existing API key's project. Good if your free credits ran out, or you'd rather pay with crypto than a card.
- **Accountless wallet** — The wallet is a separate identity. The first payment makes a fresh project named after the wallet, apart from your existing account.
**Do:** "Top up that account" → `MODE = B`. "Accountless wallet" → `MODE = A`.
---
## Step 3 — Wallet
**Ask:** (header: `Wallet`) — question: `Do you have a wallet ready, or should I set one up?`
- **I have a funded wallet** — An EVM wallet (MetaMask, Rabby, Coinbase Wallet, Frame, Phantom, …) with USDC on Base mainnet.
- **Walk me through it** — I'll guide you through making a wallet, adding Base, and buying USDC.
- **Make a fresh one** — I'll generate a throwaway wallet for automation. You'll still need to fund it.
Branch on the answer.
### Path A — "I have a funded wallet"
**Do:** Check `.env` is in `.gitignore`; add it if missing.
**Ask:** (header: `Add key`) — put the note and the question both in the `question` field:
> Your wallet's private key needs to go into `.env`. You can paste it here and I'll add it for you, or add it yourself. Heads up: anything pasted in chat is saved in the transcript, so for a high-value wallet, adding it yourself is a bit safer. How do you want to do it?
- **Paste it here** — Paste your private key in the chat and I'll write it to `.env` for you.
- **I'll add it myself** — You add it to `.env`, then send me just your public address.
**If "Paste it here":**
**Do:** Write `BROWSER_USE_X402_PRIVATE_KEY=<pasted key>` to `.env` (create the file if needed; make sure `.env` is gitignored). Never echo the key back or print it anywhere.
**Say:**
> Saved your key to `.env` — I won't print it back.
**Do:** Go to Step 4.
**If "I'll add it myself":**
**Say:**
> Add this line to your `.env`, then send me your wallet's public address (the `0x…` one — safe to share):
> ```
> BROWSER_USE_X402_PRIVATE_KEY=<your private key>
> ```
**Do:** When they send the address, check it matches `^0x[0-9a-fA-F]{40}$`.
**Say:**
> Got it: `<address>`. That's a valid address.
**Do:** Go to Step 4.
### Path B — "Walk me through it"
**Say:**
> 1. Install MetaMask (or Rabby, Coinbase Wallet, Frame, Trust Wallet, Phantom, …) from the official site only: https://metamask.io. Make a wallet, save the seed phrase offline, set a password.
> 2. Add Base as a network. Open https://chainlist.org/chain/8453 → "Connect Wallet" → "Add to MetaMask", then approve it in your wallet.
> 3. Click "Buy" in your wallet. Pick USDC, network Base, pay with card / Apple Pay / bank. The USDC lands straight in your wallet.
> 4. Get the private key: account menu → Account details → Show private key → enter password → copy.
> 5. Add it to your `.env` (make sure `.env` is gitignored):
> ```
> BROWSER_USE_X402_PRIVATE_KEY=<your private key>
> ```
> 6. Send me your wallet's public address (the `0x…` one) so I can check it.
**Do:** Then follow Path A from the address check onward.
### Path C — "Make a fresh one"
**Do:** Generate a wallet. Save the key to `.env`. Show the address only.
Python:
```bashFrom browser-use/browser-use, MIT.
More from browser-use/browser-use
- 0.891score
open-source
browser-use
Documentation reference for writing Python code using the browser-use open-source library.
SkillAFreshness: A★ 119KClaude Code +9 - 0.891score
cloud
browser-use
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation.
SkillAFreshness: A★ 119KClaude Code +9 - 0.891score
qa
browser-use
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence.
SkillAFreshness: A★ 119KClaude Code - 0.882score
browser-use
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
SkillAFreshness: A★ 119KClaude Code +9 - 0.878score
remote-browser
browser-use
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
SkillAFreshness: A★ 119KClaude Code +9 - 0.873score
Browser Use
browser-use.comOfficial
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
ConnectorAFreshness: ARemoteLocal★ 119K↓ 1.5M/wkClaude Code +5 - 0.748score
AGENTS.md · browser-use/browser-use
browser-use
AGENTS.md from browser-use/browser-use: 1018 lines covering 1.
TemplateAFreshness: A★ 119KCodex +5 - 0.748score
CLAUDE.md · browser-use/browser-use
browser-use
CLAUDE.md from browser-use/browser-use: 164 lines covering High-Level Architecture, Development Commands, Code Style, CDP-Use and more.
TemplateAFreshness: A★ 119KClaude Code - 0.744score
Browser Use
Browser Use
Open-source browser agent in Python, plus a hosted cloud with stealth browsers and an agent API
AgentAFreshness: A★ 119K↓ 1.5M/wk
Compare and alternatives
Featured in
Signals
- Stars
- 119,023
- Forks
- 13,223
- Open issues
- 183
- Contributors
- 383
- Last commit (this folder)
- Jun 1, 2026 (4 months ago)
- Last release
- Oct 15, 2026 (11 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/browser-use/browser-use
- Website
- browser-use.com
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from browser-use
- 0.891score
cloud
browser-use
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation.
SkillAFreshness: A★ 119KClaude Code +9 - 0.891score
qa
browser-use
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence.
SkillAFreshness: A★ 119KClaude Code - 0.891score
open-source
browser-use
Documentation reference for writing Python code using the browser-use open-source library.
SkillAFreshness: A★ 119KClaude Code +9 - 0.882score
browser-use
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
SkillAFreshness: A★ 119KClaude Code +9 - 0.878score
remote-browser
browser-use
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
SkillAFreshness: A★ 119KClaude Code +9 - 0.859score
browser-harness
browser-use
Control a real browser via CDP: clicking, typing, navigation, logged-in sessions, JS-rendered or bot-protected pages.
SkillAFreshness: A★ 18.6KClaude Code +9
Cite this page
x402 skill. Agent Mart. https://agentmart.dev/skills/browser-use-x402 (last updated 2026-10-24)