Seven questions about web data, answered with a real run
We build small, single-purpose tools for getting data off the web and publish them on Apify Store. This site is not a brochure: each page takes one question, answers it in a few lines, and then shows a real input with the output it actually produced — with the date, the duration and what it cost.
The questions
- How do I get a list of every page URL on a website? 1,733 URLs from nodejs.org in 3 seconds, without crawling it.
- How do I take a screenshot of a web page from code? One request, one PNG, with the cookie banner out of the way.
- How do I turn my own HTML into a PDF? An A4 invoice from an HTML string, margins included.
- How do I get the tables out of a PDF as rows and columns? 34 tables out of a 28-page government form.
- How do I find out what a website is built with? 25 technologies, each with the header or cookie that proves it.
- How do I screenshot every page of a website? Two tools chained — and what the whole site would actually cost.
- How do I run these from code, or from an AI agent? One HTTP call that returns the results, and the MCP route.
How these tools are priced
You pay per result — per URL, per capture, per page, per site — and nothing else. There is no subscription, no minimum and no start fee, so a run that returns ten rows costs ten rows' worth. Work that fails is not charged: a URL that will not load, a PDF that will not download, a site that answers with a 403. That is a deliberate split — you should not pay for an answer you did not get.
What we do not build
No social media scrapers, no marketplace scrapers, nothing that collects personal data, and nothing whose job is to get around an anti-bot wall. Partly because those tools break every few weeks and we are too small to keep up with them, partly because the legal ground under them is not solid. What is left is duller and it holds still: sitemaps, screenshots, PDFs, the technology a site declares about itself.