Agent skill · software engineering · browser-use
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. 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.
Why this skill is useful
Adds executable scripts for setting up a crypto wallet and integrating with the Browser Use Cloud SDK, which are not commonly found in public documentation.
What it needs
Requires bash installed locally. About 10k tokens when loaded. Last updated 2026-08-06. 108,113 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills browser-use/x402