vaaya / tools / browserbase / create_session
Browserbase create_session for AI agents
Browserbase — Create a headless browser session via x402. Charges 0.2¢ per minute of estimatedMinutes (minimum 5). Returns sessionId + connectUrl.
varies by params per call
npx @vaaya/mcp installParameters
| Param | Type | What |
|---|---|---|
estimatedMinutes | integer | |
keepAlive | boolean | |
proxies | object |
Call it
From any MCP client with Vaaya connected, one use call:
{
"service": "browserbase",
"action": "create_session",
"params": {},
"max_cost_cents": 100
}
Or over HTTP with a Vaaya API key:
curl -X POST https://vaaya.ai/api/run/browserbase/create_session \
-H "Authorization: Bearer $VAAYA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"max_cost_cents":100}'
Notes
Native x402 — vendor-direct endpoint at `x402.browserbase.com`. Pricing is **0.2¢ per minute** ($0.12/hour) — live-confirmed against the upstream challenge. Total cost = `0.2 × estimatedMinutes` cents, rounded up. Browserbase's MPP rail returns Stripe payment-intent errors for sub-50¢ charges, so x402 is the only working settlement path. Output: `{sessionId, connectUrl, paidMinutes}`. Pair with `browserbase-release-session` (DELETE, free) when done, `browserbase-extend-session` to add more minutes, or `browserbase-session-status` (free) to check remaining time.
The facts
browserbase/create_session
varies by params — the listed figure is a cap; you pay what the provider settles. Charged only on success.
Paid per call over x402 (USDC on Base) from Vaaya’s wallet; you are debited the settled amount.
Held server-side by Vaaya; your agent never receives a Browserbase key.
More from Browserbase
Give your agents this call.
Connect Vaaya once, then describe the outcome or call it directly. Paid per call, from one balance.
npx @vaaya/mcp install