Where the catalogue comes from.

Everything here is built from public metadata, public schemas and vendor documentation. No source is scraped to manufacture page content.

Apify Store public listings

Tool titles, descriptions, categories, public user counts, run statistics and current pricing come from the public Apify Store API. These values change; the catalogue is refreshed and the check date moves with it. Apify Store content remains subject to Apify's own terms.

Published Actor schemas

Input fields, output fields and dataset views come from the Actor's public build definition and, where available, its publisher documentation. A field is counted only when it appears in the published schema. We do not infer fields from marketing copy.

Public example setups

Some pages link to public Apify task examples published for a tool. These are links to the public example pages, not data we copied into our catalogue. They are labelled as example setups, not tests we ran.

Official API documentation

API pricing, quotas, shutdown dates and legal notes come from the vendor's own documentation and changelogs. The source URL and check date appear on the page. When a vendor changes a rate, the page is updated; the content-update date does not move for a cosmetic edit.

Video metadata

The Scraper Finder YouTube channel's public RSS feed provides video titles, IDs, publish dates and thumbnails for matching embeds. Embeds use a click-to-load facade; no YouTube script loads until you press play.

Licences and attribution

Apify Store listing data and schemas: used for factual reference under Apify's terms; store links point to the original pages.
Vendor documentation: quoted facts are summarised and attributed; full terms remain with the vendor.
This site does not use OpenStreetMap data; the sister publication Get a List Of does, with ODbL attribution on every page that uses it.

If you believe a source is missing or a licence is misstated, tell us.

Last reviewed 2026-11-09.