Astegiudiziarie Properties and Details Scraper

This Actor is currently a no-request policy scaffold. Aste Giudiziarie Inlinea’s Conditions of Use were checked in Chrome on 2026-09-26. Article 4 limits access and downloads to personal, non-commercial use and prohibits automated tools for mass retrieval of documents from detailed sale records. Article 5 requires express authorization for copying protected content, and Article 6 protects the auction database and warns against extraction or reuse.

Default runs finish with status: SUCCEEDED and runStatus: SKIPPED_POLICY, zero source requests, and no dataset rows. A clean collection uses runStatus: COMPLETED, a partial collection uses PARTIAL, and a failure uses FAILED; top-level status remains SUCCEEDED when the run completed or saved real rows before a later failure. New failed KVS summaries include a stable failureCode and generic failureReason; no diagnostic rows are written. The authorization checkbox is an operator attestation only; it does not grant or verify permission and never enables requests. An attested run also remains a successful policy skip.

Eight historical source-backed auction rows remain preserved. The existing OUTPUT summary reports status: SUCCEEDED and runStatus: COMPLETED for its historical three-item run; new summaries use the same outcome-specific runStatus mapping. The rows are not verified as current or authorized for reuse. Offline parser tests use synthetic HTML only and do not establish live source coverage. Validation and runtime failures produce a FAILED summary and no diagnostic dataset rows.

npm test
npm run check
apify validate-schema

Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.