> Browser automation session
// Creates a remote browser session for web automation and scraping
Creates a remote browser session for web automation and scraping. Agents can request it by capability ID compute.browser_session, or by plain intent — EntRoute resolves phrases like “browser session”, “puppeteer” and “playwright” to this capability.
EntRoute currently lists 10+ endpoints from 7 providers for compute.browser_session, priced from $0.001 to $0.01 per call, settled in USDC on Base. The quickest responds in about 16ms at the 95th percentile. Every endpoint below is re-probed every 10 minutes for a valid 402 payment challenge; the ordering blends measured success rate, latency and price rather than provider claims.
These phrases resolve to this capability with intent-based discovery.
curl -X POST https://api.entroute.com/discover \ -H "Content-Type: application/json" \ -d '{"capability_id": "compute.browser_session"}'
https://httpay.xyz/api/user-agent-parse https://useragent.agentutil.net/v1/parse https://stableflare.dev/api/browser/json https://stableflare.dev/api/browser/content https://stableflare.dev/api/browser/markdown https://apify-dlfd68ww7-merit-systems.vercel.app/api/actors/apify/rag-web-browser/call https://archtools.dev/v1/tools/browser-task https://apify-api-git-br-apify-typed-input-schemas-merit-systems.vercel.app/api/actors/apify/rag-web-browser/call https://api.strale.io/x402/structured-scrape https://stableflare.dev/api/browser/pdf Use this capability in your agent or application:
Frequently asked questions about Browser automation session
How much does a browser automation session API call cost?
Endpoints listed for compute.browser_session on EntRoute are priced from $0.001 to $0.01 per call. Payment is per request — there is no subscription, account or API key. Prices shown are read from each endpoint's live 402 response, not from a provider-supplied catalogue.
How do AI agents pay for browser automation session endpoints?
Via the x402 protocol. The agent calls the endpoint, receives an HTTP 402 Payment Required response describing the price and recipient, signs a stablecoin payment (USDC on Base), and retries the request with proof of payment. The whole exchange takes seconds and needs no human approval.
How many providers offer browser automation session?
10+ endpoints are currently listed for compute.browser_session across 7 providers. That number moves as endpoints are added and as failing ones are demoted.
Are these browser automation session endpoints verified?
Each one is probed every 10 minutes to confirm it still returns a well-formed 402 challenge on a payable network. Endpoints whose 7-day success rate drops below 50% are moved out of the ranked list into fallbacks with an explicit exclusion reason, so an agent can decide whether to retry them.