SOURCE DOCUMENT · SHARED CAPABILITY
Full support and qualification matrix ↗
Web access provider matrix
Search, research, extraction, browser sessions and proxies keep their individual provider capabilities.
| Provider | REST | TypeScript SDK | Native MCP | Proxy |
|---|---|---|---|---|
| Bright Data | Yes | @brightdata/sdk | Hosted and local | HTTP, HTTPS, SOCKS |
| Massive | Yes | Not advertised | Not advertised | Residential HTTP, HTTPS, SOCKS |
| Browserbase | Yes | @browserbasehq/sdk + Stagehand v4 | Hosted and local | Session-managed or custom |
| Serper | Yes · ten result categories | Not advertised | Not advertised | Not advertised |
| Linkup | Yes · including x402 | linkup-sdk | Hosted and local | Not advertised |
| Tavily | Yes | @tavily/core | Hosted and local | Not advertised |
| Direct fetch | Yes | No | ContractSpec projection only | No |
| Reworkd | Yes | No public client bound | ContractSpec projection only | No |
| Firecrawl | Yes | REST preferred | Documented, not bound | No |
| Apify | Yes | REST preferred | Documented, not bound | No |
| Oxylabs | Yes | No | Local server, not bound | HTTP, HTTPS, SOCKS5/SOCKS5H |
Source documentation excerpt · adapter support is not a claim of completed live qualification
Web acquisition & scraping
Each search, scraper, browser and proxy provider exposes different methods, limits and evidence.
One governed acquisition layer with explicit provider capabilities and preserved provenance.
Who it fits & where to start
For Builders and operations teams collecting information for research, intelligence and application workflows.
A useful first step One governed acquisition layer with explicit provider capabilities and preserved provenance.
Explore Web acquisition & scraping