# Bright Data vs Decodo Web Data API (slim)

> Decodo Web Data scores 61.8 (C) to Bright Data's 56.9 (C) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bright-data-vs-decodo.md (~4,800 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/bright-data-vs-decodo.json · canonical https://www.anchorterminal.com/compare/bright-data-vs-decodo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Decodo Web Data API scores 61.8 (C) on agent readiness against Bright Data's 56.9 (C), and leads in 3 of 7 scored categories. Bright Data leads on schema & documentation and security & auth. Both do scraping.

- Bright Data: C 56.9, rank #812 of 1486 · https://www.anchorterminal.com/tools/bright-data.min.md
- Decodo Web Data API: C 61.8, rank #591 of 1486 · https://www.anchorterminal.com/tools/decodo.min.md
- Bright Data, good for Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume. Ahead on Schema & documentation, 74 against 67; Security & auth, 69 against 45.
- Decodo Web Data API, good for Agents that need pages, Google results and e-commerce or social templates through one key with published per-1,000 prices and a free plan. Ahead on Reliability, 59 against 40. Also Runs on your own machine; No incidents deducted, where Bright Data loses 6 points for them.

| Category | Bright Data | Decodo Web Data API |
| --- | --- | --- |
| Reliability (16%) | 40 | 59 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 74 | 67 |
| Agent ergonomics (13%) | 79 | 82 |
| Security & auth (14%) | 69 | 45 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 87 | 85 |
| Transparency & trust (7%) | 61 | 62 |

| Fact (where they differ) | Bright Data | Decodo Web Data API |
| --- | --- | --- |
| Vendor | Bright Data | Decodo (UAB "Data troops") |
| Hosted endpoint | `https://api.brightdata.com/request` | `https://mcp.decodo.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Price for scraping | not published | $0.50 per 1,000 requests |
| Tools exposed | 32 | 33 |
| MCP registry | `io.github.brightdata/brightdata-mcp` | `io.github.Decodo/mcp-server` |
| Last release | 2026-11-02 | 2026-10-30 |
| Terms last updated | 2026-06-16 | 2025-06-16 |
| Privacy policy last updated | 2026-05-14 | 2026-05-21 |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 2.6k stars | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Security & auth, Bright Data +24: Bright Data 69 (API keys carry one of five roles (Admin, Finance, Ops, Limit, User), can be given an expiry, and are revoked or refreshed in the control panel, and the hosted MCP also takes OAuth 2.1 with PKCE and one `mcp` scope (30). The README's default hosted setup still puts the key in the URL as `?token=`, a documented option, so less 10 (20). User-role keys can't change configuration, tools load by group, and tools carry readOnlyHint and destructiveHint, but browser tools can fill forms and click with no confirmation step from the server (14 of 20). Since 3.1.0 results from search, scrape, scraper, dataset and browser tools are wrapped as untrusted web content with a per-call marker, and since 2.12.0 a content gate, documented in the README and on by default, asks the user through MCP elicitation before returning page text that looks like instructions to change the MCP configuration (12 of 15). The MCP `session_stats` tool reports calls in a session. We didn't find a per-request log for operators (5 of 15). ISO 27001, 27017 and 27018, SOC 2 Type II under NDA, a public SOC 3, a managed private bug bounty and security fixes in the MCP changelog per the 1 October check. No security.txt (404 on 4 November). OSV holds no advisory for @brightdata/mcp (18 of 20). 20+14+12+5+18 = 69.); Decodo Web Data API 45 (One Bearer API key per Web Data API subscription with no scopes, and no rotation or revocation steps found in the reviewed docs. The hosted MCP server adds OAuth 2.1 with PKCE and dynamic registration, but its metadata advertises no scopes. No query-string credential is documented (20 of 30). Scraping only reads, and the MCP tools are annotated read-only, but `http_method: POST` sends requests to target sites and there is no read-only key (8 of 20). No guidance on treating scraped content as untrusted was found in the docs or the MCP README (0 of 15). The dashboard statistics API reports traffic by target, and each response carries an `x-task-id`. No per-call audit log (7 of 15). ISO/IEC 27001:2022 for proxies and the Scraping API, a SafeBase trust centre and KYC at signup. security.txt answers 404 and no disclosure policy or bug bounty was found (10 of 20). 20 + 8 + 0 + 7 + 10 = 45.)
- Reliability, Decodo Web Data API +19: Bright Data 40 (No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). The SERP API fair-use page gives 1,000 requests a minute for unfunded accounts with HTTP 429 above it and a header that reads the account's limit, paid Web Unlocker plans state unlimited concurrency, and the free tier is 5,000 requests a month (15). The Web Unlocker error catalogue documents a 429 `sr_rate_limit` when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10). 0+5+15+10+0+10 = 40.); Decodo Web Data API 59 (Graded on the hosted lines. Instatus page at status.decodo.com with Web Data API and each legacy scraping API as components, with RSS history (20). In the 90 days to 6 November, every scraping API was out for 2 hours 51 minutes on 30 October, the main outage, with outages of 13 minutes on 26 October and 21 minutes on 15 October across the same components. The rest of the incidents hit proxies, payments or the website. One major (10). Per-plan request rates are published, 10 to 200 a second, though the same page's FAQ says paid plans support 10 to 50 (12 of 15). The response code table tells the agent to wait a couple of minutes on 429 and to retry 500, 524 and 613, which aren't billed, and the MCP client backs off exponentially. No Retry-After or idempotency guidance (7 of 15). No SLA; the License Agreement disclaims uninterrupted service (0). Web Data API is the current, unflagged product (10). 20 + 10 + 12 + 7 + 0 + 10 = 59.)
- Schema & documentation, Bright Data +7: Bright Data 74 (No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of `run_scraper` (14 of 20). Typed inputs with enums such as engine (bing or google), time_range and format (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, now dated to 27 October 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0, per the 1 October reading (10 of 15).); Decodo Web Data API 67 (No OpenAPI or similar contract for the Web Data API; the two published specs cover the proxy account API and dashboard statistics. The MCP server types every input with zod (12 of 25). llms.txt indexes 401 guide pages, each served as Markdown (10). Tool descriptions state purpose and when to use a tool, such as scrape_as_markdown 'when no site-specific tool fits', and link the docs page (14 of 20). Parameters are tabled with defaults, with enumerated proxy_pool, headless and device_type, but `headers` is a free object and POST bodies are base64 strings (10 of 15). Curl examples on every page, a response code table with fixes and billing, and parser status codes (14 of 15). Paths are versioned at /v1 and the MCP server's releases are tagged by semantic-release, but no API changelog was found (7 of 15). 12 + 10 + 14 + 10 + 14 + 7 = 67.)