Pay per Request Browser
Sets up pay-per-request Browser Use Cloud access from a crypto wallet.
Install
npx skills add browser-use/browser-use --skill x402 -g -a claude-code -y- Repository
- browser-use/browser-use120k
- Category
- Business
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
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.
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
questionfield (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 thequestionfield, 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) andMODE(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:
