Who builds these Actors
Oswaldo Carabano — Actor developer. This site is the documentation for the 2 public Apify Actors on my profile, plus the measurements that did not fit in a README.
What I build
Actors for extracting public web data: Python, Playwright and Crawlee on the Apify platform, with documented input schemas, structured output and error messages that say what went wrong. Two are public today — a Nextdoor business and reviews scraper, and a coches.net car listings and dealer scraper — and the catalogue grows one target at a time rather than by generating variations.
How I work
Every Actor here is built on the same three constraints, and they are constraints rather than features because each of them costs something:
- No credentials. The Actors read only what the target site serves a signed-out visitor. That rules out anything behind a login, permanently. In exchange there is nothing to expire, so a scheduled run does not have a failure date nobody wrote down.
- Measured, not asserted. Every documented field carries a fill rate counted on a real sample. When a re-measurement on a larger sample came out worse, the worse number replaced the better one — see methodology.
- The site's rules are the specification. robots.txt is downloaded and obeyed on every run. Where it caps pagination, coverage comes from breadth instead of depth, and where the public data genuinely is not reachable, the Actor reports that instead of working around it.
Why this site exists
An Apify README is the right place for the summary and the wrong place for a 55-field reference, a fill-rate table and the reasoning behind a privacy decision. This site holds those, along with 24 guides about the data itself: what each field means, how often it is populated, and which obligations attach to which category of data.
It is a first-party source. I document my own Actors here, which means you should read the measurements as evidence and not as an independent review — and it is why every figure is published with the sample size and method that produced it, so you can check rather than trust.
What I do not claim
- I am not a lawyer. The compliance articles explain the reasoning behind engineering decisions and cite the law they rest on; they are not legal advice.
- No Actor here is affiliated with the sites it reads. Nextdoor, coches.net and Adevinta Spain have no relationship with this project.
- A measurement describes the run it came from. Target sites change their markup and their limits without notice, so a figure from August 2026 is evidence about August 2026.
Getting in touch
Bugs, missing fields and target requests all go to the same place: hello@actorstack.dev. If you want an Actor for a site that is not covered yet, describe the data you need — the scope and the honest limits get written down before any code does. Data removal requests go to privacy@actorstack.dev and are handled as described on the data removal page.
Elsewhere
Apify profile: apify.com/oswaldocarabano. That is the canonical, runnable home of every Actor; this site is its documentation.