Decodo review

Decodo is a hosted web data platform, not a scraping library or a self-hosted server. Its Web Data API exposes four functions under one key: scrape a page, search the live web, map a site’s URLs and crawl multiple pages. The service returns web content in structured formats, including Markdown or JSON, for downstream applications such as RAG pipelines and AI agents.

The API sits between your application and public websites. Decodo handles collection and, for crawls, automatic link following and JavaScript rendering; its proxy network provides IP access and location targeting for projects that need it. The vendor lists 125M+ IPs worldwide and coverage across 195+ locations. You can use the API as an agent tool through MCP or call it from an application using the supported SDKs. This setup avoids operating a scraper fleet yourself, but makes your collection path dependent on a hosted vendor and its access to each target.

The Web Data API groups four endpoints under one key: /scrape, /search, /map and /crawl. The homepage lists HTML, JSON or Markdown for scrape results, and describes structured Markdown or JSON output for LLM workflows. Search can retrieve results from Google, Bing and other engines; crawl supports multi-page collection, automatic link following and JavaScript rendering.

Decodo lists Python and TypeScript SDKs, an official MCP server, a CLI, agent skills, and integrations for n8n, LangChain, LlamaIndex and OpenClaw. The CLI can run endpoints from a terminal or shell script, including in CI jobs. The homepage describes MCP setup through configuration and says the server is listed in GitHub’s MCP Registry. Use the vendor docs to confirm authentication, parameters, response handling and SDK coverage for your language before implementation; the homepage directs developers to its SDK and setup pages. The integration menu is broad, but teams using other languages should confirm SDK support in the vendor’s docs.

The pricing page lists a free monthly plan with 10 req/s and up to 5K crawls or 10K pages. Paid monthly plans start at $19 for Regular — 10 req/s, with up to 19K crawls or 38K pages. The other tiers are Regular — 25 req/s at $49 (65K crawls or 122K pages); Regular — 50 req/s at $99 (141K or 330K); Regular — 100 req/s at $249 (383K or 1.2M); and Regular — 150 req/s at $499 (831K or 2.7M).

Higher tiers list Regular — 200 req/s at $999, with up to 1.8M crawls or 6.2M pages, and another Regular — 200 req/s plan at $1,499, with up to 2.9M crawls or 9.9M pages. Enterprise is custom. Separately, the homepage advertises Web Data API access starting at $0.15 per 1K requests; confirm how that rate relates to the monthly plans. The pricing page lists monthly prices, with no annual billing shown. It does not list add-ons or overage rates, so confirm the cost of usage beyond plan limits before launch.

Decodo is presented as a hosted API and proxy service. The vendor doesn’t publish an open-source licence or a self-hosting option, so teams should treat the collection service as a hosted dependency unless Decodo confirms otherwise. The homepage lists an official MCP server and SDKs, but that alone does not establish that their source code is open under a particular licence.

The API returns content in formats such as Markdown and JSON, which you can store in your own systems and use to reduce dependence on Decodo’s output pipeline. The vendor doesn’t publish a data-export or migration process. A move to another provider would likely require replacing API calls, adapting request and response handling, and switching proxy settings. Keep your own copy of collected data and isolate provider-specific code behind an internal interface if portability matters.

Decodo’s homepage advertises 99.99% uptime and, separately, 99.99% success on difficult anti-bot targets. Treat these as vendor claims, not a substitute for a written SLA or measurements against your target sites. The listed plans impose both request-per-second limits and monthly crawl or page caps, so production systems need usage monitoring and backpressure. Ask the vendor how requests beyond a plan’s included capacity are handled and priced.

The proxy network lists 195+ locations and city-level targeting, while new features mention state, city and ASN targeting for datacenter and ISP proxies. Coverage can still depend on proxy type and inventory. In one Reddit thread, a user looking for a static ISP proxy said Decodo and other providers did not seem to offer the state-level targeting they needed. Verify the exact location and target combination before relying on it. The vendor also describes CAPTCHA handling and anti-bot access; test against your own targets and review applicable site terms, privacy requirements and data-handling obligations.