FetchRelay is a web data workspace that aims to simplify the process of extracting content from websites, collecting structured product fields, and crawling entire sites. The service provides an API-first approach, letting developers send a URL and receive parsed, usable data in return.
What FetchRelay does
The core workflow is straightforward: you point FetchRelay at a URL, it fetches the page, and you inspect the result before using it in your application. The service handles the messy parts of web scraping, including JavaScript rendering, anti-bot protections, and output formatting, so developers do not have to build and maintain their own scraping infrastructure.
For product data collection, FetchRelay lets you define which fields to extract from a page, turning unstructured HTML into structured records. For site-wide crawling, the service can traverse an entire domain and pull content from multiple pages according to rules you specify.
The API endpoint, POST /api/scrape, accepts a URL and returns the extracted data. Session activity tracks requests from your browser session, giving visibility into what has been fetched and how.
Free tier and getting started
FetchRelay offers a free tier with 100 monthly credits and no credit card required. You can try the service against a public URL without signing up, which lowers the barrier for evaluating whether it fits your use case. Credits are consumed per request, and the free tier is enough for light prototyping or small-scale data collection tasks.
For projects that need more volume, the paid tiers scale up from there. The pricing structure is not detailed on the landing page, but the free tier gives developers a hands-on way to test the API before committing.
Where it fits in the scraping landscape
Web scraping remains a common need for developers building price comparison tools, market research platforms, content aggregators, and lead generation systems. Running your own scraper means dealing with rotating proxies, headless browsers, CAPTCHA solving, and constant maintenance as target sites change their markup. Services like FetchRelay abstract that complexity behind an API call.
The tradeoff is control and cost. Self-hosted scraping gives you full discretion over what you fetch and how, but requires ongoing engineering effort. A managed service reduces that burden but introduces a dependency on a third party and a per-request cost. For teams that need reliable data extraction without building a dedicated scraping pipeline, FetchRelay presents one option worth evaluating.
The service is live now at fetchrelay.com, and the free tier is available immediately for anyone who wants to test it against a public URL.