Browser tools
MCP
Browserbase
Give an agent a browser session.
Free tier
Steel x402
Scrape, screenshot or render pages using wallet payments.
THE OVERVIEW
What you can build with it.
Steel documents x402 browser actions for rendered page content, screenshots and PDFs. Calls use per-request USDC payments rather than a Steel account or API key.
Scrape rendered pages
Capture page screenshots
Render pages to PDF
A CLEARER NEXT STEP
Your connection guide.
Documentation reviewedConnection not tested by ToolSkipperTask outcome not independently tested
Reviewed 13 October 2026. Choose the connection that fits your agent host. Provider instructions and limits may change.
x402 wallet payment over HTTPSREST · https
Provider endpoint
https://x402.steel.dev/v1/scrapeAuthentication · required
A wallet payment replaces account/API-key access. Steel documents Base or Solana USDC. Its example uses X-PAYMENT, while the observed endpoint returned a V2 PAYMENT-REQUIRED challenge; confirm a compatible current client before signing.
Steel x402 documentationRelay unpaid HTTP 402 observation: Steel scrapePOST JSON with a public target url to /v1/scrape; format may include markdown. The provider also documents /v1/screenshot and /v1/pdf.
Steel x402 documentationBefore any signed retry, confirm the current x402 client, payment header and resource routing with Steel; the observed challenge differs from the documentation example.
Steel x402 documentationRelay unpaid HTTP 402 observation: Steel scrapeInspect the current challenge amount, asset and network. Payment requires funded USDC on Base or Solana and explicit spending authorization.
Steel x402 documentation
Allowances and costs
The provider documents $0.01 USDC per request on Base or Solana mainnet. An unpaid scrape challenge quoted 10,000 USDC atomic units. A funded wallet and permission to spend are required.
Free access: No free task execution is documented for this payment route. An unpaid challenge does not return the requested content.
- Documentation lists $0.01 per request; read current challenge terms before spending.
- Only the scrape payment challenge was inspected. Screenshot, PDF output and payment settlement were not tested.
What still needs checking
- Documentation was reviewed; a paid provider task was not tested. The unpaid challenge proves a payment request was returned, not successful browser execution.
- The observed challenge resource URL is https://api.paysponge.com/v1/scrape, different from the requested Steel URL. The docs' payment-header example also differs from the observed protocol version. Resolve these with the provider before signing.
- Relay provides discovery and setup information only; it has no wallet, signing or paid execution adapter for this service.
Catalogue snapshot.
The listing below retains its original source evidence. The connection guide above separately documents provider options and their review date.
Listed interfacesREST · x402
Listed authenticationWallet payment
Pricing modelUsage-based
Primary categoryBrowser tools
Documented endpoint
https://x402.steel.dev/v1/scrapeCheck the provider’s setup instructions and authentication requirements before connecting.Know where it comes from.
This record is based on the provider’s published documentation. Source retrieval is distinct from a successful service test.
Evidence levelProvider documented
Source checked13 October 2026
SourceView provider source
An unpaid scrape request returned x402 V2 HTTP 402 on 13 October 2026; no payment or browser output was produced. The challenge resource was api.paysponge.com/v1/scrape, while Steel's example names x402.steel.dev and older X-PAYMENT. Confirm current routing and client compatibility before signing. Relay cannot pay or execute this route.