Build from verified surfaces
These snippets use BrowserCity public routes and product pages already present in the website: MCP, Humanized REST, pricing calculator, and trust resources.
Templates
Start from a working pattern.
Practical starting points for agents, extraction jobs, authenticated handoffs, and Playwright flows. We keep the snippets provider-neutral and call out the cost assumptions before you scale them up.
01
MCP for model-native browser tools
02
Humanized REST for queue-friendly browser actions
03
Sessions API for Playwright-compatible control
Library
Browser automation templates
Small, composable examples that map to current BrowserCity surfaces: MCP, Humanized REST, Sessions, and Playwright-compatible connections.
MCPStarter
Agent web research brief
Give an MCP-capable agent a hosted browser loop for source discovery, page inspection, and cited research notes.
Cost assumptionCosts depend on browser session time and proxy traffic. Start with a short managed datacenter session, then model longer or higher-fidelity runs in the pricing calculator.
Humanized RESTIntermediate
Browser Flow branch workflow
Run a bounded Humanized REST workflow as one serial, single-session request with explicit success and failure transitions.
Cost assumptionEstimate cost from the effective session runtime and traffic. Flow does not add a separate provider-specific fee or roll back already completed usage.
MCPStarter
MCP browser setup for coding agents
Connect coding agents — Claude Code, Cursor, Windsurf, Codex — to a BrowserCity stealth browser over MCP with one config block.
Cost assumptionAgent-driven sessions are usually short but frequent. Watch session time per task in usage views before raising agent parallelism.
MCPStarter
Personal agent browser setup
Give a personal AI assistant — OpenClaw, Hermes, and similar — stealth browsing through a BrowserCity skill file plus MCP or REST.
Cost assumptionPersonal browsing is bursty: a few short sessions per task. Cost tracks how often the agent browses, not how complex each page is.
Humanized RESTStarter
Page-to-markdown extraction job
Turn a list of URLs into clean markdown records through the Humanized REST /v1/do/* layer.
Cost assumptionEstimate cost from total browser session time and traffic. Keep early batches small, then use the pricing calculator once you know average page weight and runtime.
Request APIStarter
Scrape a JavaScript-heavy page
Extract clean markdown from a client-rendered page with one Request API call — no browser orchestration code.
Cost assumptionSingle-page extractions are the cheapest primitive: short render time plus page traffic. Model batch volume in the pricing calculator before scheduling large crawls.
Sessions APIIntermediate
Authenticated workflow handoff
Capture authenticated browser storage once, then reuse that storage in a later managed session so repeat workflows start signed in.
Cost assumptionCosts are driven by how long the capture and reuse sessions stay open and how much traffic the logged-in flow produces. No extra provider-specific fees are assumed here.
PlaywrightIntermediate
Authenticated portal download
Log in to a portal, navigate to a report, and save the downloaded file — the recurring export job with no API behind it.
Cost assumptionLogin plus one download is a short session; the file's size drives traffic cost. Large report exports over residential egress are the case to model first.
PlaywrightStarter
Playwright session control
Move an existing Playwright script from local browser launch to a BrowserCity managed session.
Cost assumptionModel one browser session per worker. Cost follows browser hours plus any managed or BYOP traffic selected in the session request.
PlaywrightIntermediate
Form submission with file upload
Fill a portal form, attach a file, and submit it from a cloud Playwright session — the pattern behind most back-office automation.
Cost assumptionForm workflows are short sessions with small traffic. Cost scales with how often the workflow runs, not with form complexity.
Humanized RESTIntermediate
Geo-localized content check
Open the same page through residential egress in different countries and compare what each market actually sees.
Cost assumptionResidential traffic is priced above datacenter traffic. Keep checks to the pages you actually monitor and reuse one session per country.
Request APIStarter
Page change monitor
Render a page on a schedule, hash the markdown, and alert only when the content actually changes.
Cost assumptionCost is check frequency times page weight. Hourly checks on a handful of pages cost cents; tighten the interval only where changes matter that fast.
Sessions APIIntermediate
Parallel browser sessions
Fan a URL list across several cloud browsers at once and collect results as each session finishes.
Cost assumptionParallelism changes wall-clock time, not total cost: ten sessions for one minute cost the same compute as one session for ten minutes.
Assumptions stay visible
Templates avoid benchmark promises and provider-specific mechanics. Replace placeholder domains, storage state, and API keys with values from your own application.
[ 08 / 08 ] — Get Started
Give your AI agents the web.
We're in private beta — request access and we'll get you set up. Private sessions by default.