Frequently asked questions

Pry is an adaptive web-scraping engine with a 12-tier escalation ladder — it starts with a cheap plain HTTP request and only climbs to stealth browsers when a site fights back. Cloudflare, DataDome and Akamai are handled automatically. The same engine powers our 94 Apify Actors and the x402-gated API.

Add target URLs, click Start (or POST to /v1/scrape), and results stream into the dataset as each URL finishes. Export as JSON/CSV/Excel or consume via API and webhooks. Full walkthroughs live under Getting started.

Yes — scheduling, monitoring and API access are first-class Apify platform features. Monitoring Actors pair especially well with hourly or daily schedules: the first run captures a baseline, after that you only hear about actual changes.

It depends on the Actor — and we publish it either way. Our API-backed Actors (GitHub releases, npm/PyPI stats, App Store reviews, domain records, FX rates) document their exact public endpoints in the README. Extraction Actors read schema.org JSON-LD the target site already embeds. No magic, no silent breakage.

Your dataset says skipped with the reason — never a fabricated row. You can audit every cent: each dataset item carries its status, method tier and timestamp.

Every extractor is back-tested against live sites before publishing. That process caught a parser bug affecting millions of WordPress sites (unquoted JSON-LD) before launch — see our live-fire verification log.

Pay-per-event from $0.50 per 1,000 results. No subscriptions, no minimums. Monitoring Actors charge less for quiet checks; you pay for outcomes, not for our compute struggle.

Yes — for bulk pipelines or private deployments contact [email protected].

We stick to publicly available data and documented sources, respecting robots.txt, ToS and privacy law. The self-hosted Pry core ships compliance tooling: consent handling, deletion and retention controls.

Open core, MIT-licensed, self-hostable — source at codeberg.org/cryptorugmunch.