This integration uses the HTTP 402 Payment Required status code to enable seamless crypto payments for browser automation.
https://x402.browserbase.com
Key features
No account required
Start using browser sessions immediately without signing up or managing API keys
Pay-per-use
Only pay for what you use with transparent per-minute pricing
Crypto native
Pay with USDC on Base network using any EVM-compatible wallet
Instant access
Receive WebSocket connection URLs immediately after payment
How it works
Request
Make a request to the x402 endpoint. The server returns payment requirements with a 402 response.
Pricing
| Duration | Cost (USDC) |
|---|---|
| 5 min | $0.01 |
| 15 min | $0.03 |
| 30 min | $0.06 |
| 60 min | $0.12 |
Requirements
Network
Base (mainnet)
Token
USDC (
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)Wallet
Any EVM wallet with USDC on Base
Use cases
Quick prototyping
Test browser automation without commitment or account setup
Anonymous usage
Run browser sessions without creating an account or sharing personal information
Crypto-native apps
Integrate browser automation into Web3 applications with native payment flows
Pay-as-you-go
Ideal for irregular usage patterns where subscription plans don’t make sense
Premium features with AgentKit
By default, x402 sessions use a standard browser. To unlock Verified browsers — the same premium feature available to Scale plan customers — your agent can prove it’s human-backed using AgentKit from Tools for Humanity.Standard x402 session
Pay with USDC, get a working browser. No account or identity required.
Verified x402 session
Add an AgentKit proof header to unlock Verified browsers.
Set up AgentKit verification
Learn how to prove your agent is human-backed and unlock premium features
Getting started
Ready to start using pay-per-use browser sessions? Check out the quickstart guide to create your first session.Quickstart guide
Create your first x402 browser session
x402 Protocol
Learn more about the x402 payment protocol