Guides, comparisons & integrations
Practical docs-style writeups for shipping: migration guides, API recipes, and competitor breakdowns.
Blog
DocsRequest API vs Sessions vs Humanized REST vs MCP
A practical decision guide for choosing between /v1/requests, /v1/sessions (Playwright), /v1/do humanized tools, and the MCP browser server.
Why we built browser.city
Browser infrastructure is full of pricing traps and privacy ambiguity. We built browser.city on stealth-by-default, zero logs, and APIs that stay simple.
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 Bright Data: stealth browsers vs proxy empire
Bright Data is the enterprise proxy giant with many data products. browser.city is focused stealth browser infrastructure with simpler primitives.
browser.city vs Browser Use: framework vs infrastructure
Browser Use is an agent framework for browser control. browser.city is stealth browser infrastructure — sessions, requests, MCP. How they fit together.
browser.city vs Browserbase (2026): stealth, pricing, APIs
A practical, engineering-first comparison for teams choosing a browser API for agents, scraping, or automation.
browser.city vs Browserless: what changes in 2026
Browserless is the OG browser API. browser.city is infra-first stealth + zero-logs. Here’s how to choose.
browser.city vs Firecrawl: browsers 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.
Integrations
View allUse browser.city with OpenClaw (skills + stealth browsing)
Add browser.city to OpenClaw as a skill-backed browser backend when you need stealth rendering, remote interaction, or clean markdown extraction.
Use browser.city with Apify (Actors + Crawlers)
Run large-scale crawling in Apify while delegating stealth browsing, extraction, and proxy egress to browser.city.
Use browser.city in Claude Code via MCP (remote server)
Add browser.city as an MCP server in Claude Code so your agent can browse, click, and extract markdown against real stealth browsers.
Use browser.city in Cline (VS Code) via MCP
Configure the browser.city hosted MCP server in Cline so your VS Code agent can browse, click, and extract markdown with real browsers.
Use browser.city in Codex (OpenAI Codex CLI) via MCP
Configure browser.city as an MCP server in Codex so your coding agent can open real browsers, navigate, click, and extract markdown on demand.
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.
Give your AI agents the web.
We're in private beta — request access and we'll get you set up. Private sessions by default.