Web access and residential proxy
One governed contract surface for scraping, search, research, browsers, and proxies.
Bright Data, Massive, Browserbase, Serper, Linkup, and Tavily share normalized results and policy controls while preserving every documented vendor-native transport.
Compatibility rule
Native when documented · ContractSpec MCP for every normalized operation
Each supported cell pins its official documentation excerpt, evidence packet, exact operations, adapter symbol, and fixture tests. Missing SDK, webhook, WebSocket, SSE, MCP, or proxy surfaces are marked unsupported.
Shipped providers
Bright Data
Broad scraping, browser automation, delivery callbacks, and standalone residential proxies.
REST · official SDK · webhook · CDP · hosted/local MCP · HTTP/HTTPS/SOCKS proxy
Massive
REST-first search and browser rendering with polling, callbacks, usage, and proxy access.
REST · callback · CDP · ContractSpec MCP · HTTP/HTTPS/SOCKS proxy
Browserbase
Managed browser sessions, persistent contexts, Search, Fetch, CDP, and per-session proxies.
REST · official SDK · CDP · hosted/local MCP · managed/custom session proxy
Serper
Focused Google result APIs across ten search and discovery categories.
REST · ContractSpec MCP
Linkup
Agent-oriented search, fetch, asynchronous sourced research, tasks, and x402 authorization.
REST · official SDK · polling · hosted/local MCP · x402
Tavily
Search, extraction, mapping, crawling, and research with polling or server-sent events.
REST · official SDK · SSE · hosted/local MCP with API key or OAuth
Safety baseline
Governed, provider-pass-through, and public-only modes all block embedded credentials, loopback, private, link-local, and metadata targets. Control APIs require HTTPS; redirects, bodies, retries, SSE events, and browser lifetimes are bounded.
Credentials resolve through SecretProvider. CDP URLs, cookies, proxy passwords, MCP credentials, wallet keys, and callback tokens never enter serialized contracts, fixtures, logs, or telemetry.
Recommended next wave
Apify
Next broad-coverage candidate for Actors, crawling, webhooks, MCP, and proxy pools.Firecrawl
Strong next fit for agent-ready crawl, extract, asynchronous delivery, and MCP workflows.Oxylabs
Strongest next proxy-focused candidate for residential networks, unblockers, and browsers.These are recommendations rather than shipped adapters. Each should enter the same contracts-first capability-evidence workflow before promotion.