Guides, comparisons & integrations
Practical docs-style writeups for shipping: migration guides, API recipes, and honest competitor breakdowns.
Blog
DocsRequest API vs Sessions vs Humanized REST vs MCP: what should you use?
A practical decision guide for choosing between /v1/requests, /v1/sessions (Playwright), /v1/do (humanized tools), and MCP.
Why we built browser.city
Browser infrastructure is full of pricing traps and privacy ambiguity. We built browser.city around stealth-by-default, zero logs, and APIs that stay simple at scale.
Comparisons
View allbrowser.city vs Anchor Browser: stealth vs verified access
Anchor Browser’s Cloudflare Verified Bot direction is a different future than adversarial stealth. Here’s how it compares to browser.city today.
browser.city vs Browserless: what changes in 2026 (and why it matters)
Browserless is the OG browser API. browser.city is infra-first stealth + zero-logs. Here’s how to choose.
browser.city vs HyperBrowser: infra primitives vs agent-first platform
HyperBrowser is positioned as “web infra for AI agents.” browser.city is stealth-by-default browser infrastructure with Request API + MCP. Compare the tradeoffs.
browser.city vs Steel.dev: stealth is table stakes, UX is not
Steel.dev is a polished, AI-agent-friendly browser infra product. Here’s how it compares to browser.city across pricing, APIs, and operational defaults.
browser.city vs Firecrawl: browser infrastructure vs extraction API
Firecrawl is an extraction-first API for LLM-ready web data. browser.city is stealth browser infrastructure with an extraction-friendly Request API. Here’s how to decide.
browser.city vs Browserbase (2026): stealth defaults, pricing, and APIs
A practical, engineering-first comparison for teams choosing a browser API for agents, scraping, or automation.
Integrations
View allUse browser.city with OpenClaw (skills + stealth browsing)
OpenClaw already has web_fetch and browser tools. Add browser.city as a skill-backed browser backend when you need stealth rendering, remote interaction, or clean markdown extraction.
Use browser.city with CrewAI (tools + browsing)
Give CrewAI agents a fast web-reading tool via the Request API, and use Humanized REST (/v1/do/*) when interaction is required.
Use browser.city in Windsurf via MCP (remote server)
Configure browser.city as an MCP server in Windsurf so your agent can browse, click, and extract markdown with real remote browsers.
Use browser.city with LangChain (RAG + agents)
Fetch clean markdown with the Request API, then feed it into LangChain documents and pipelines. Use Sessions/Humanized REST only when interaction is required.
Use browser.city in Cursor via MCP (project or user config)
Connect Cursor to the hosted browser.city MCP server so your editor agent can open real browsers, navigate, click, and extract markdown.
Use browser.city with Playwright (Sessions API)
Connect Playwright to a hosted browser.city session. Keep your Playwright scripts and get stealth, egress control, and predictable browser infrastructure.
Start building in under a minute
Free tier. No credit card. Full stealth from day one.