ScraperAPI

Uses AI; provider not disclosed. not model-free after all — the June 2026 release note 'Introducing AI Parser' and docs.scraperapi.com/ai-parser describe an API at aiparser.scraperapi.com that takes up to 3 example URLs, generates a custom parser tailored to the page layout, and extracts structured JSON with no CSS/XPath selectors, costing 30,000 credits per parser; no docs page names the model or provider behind it. We checked and found no first-party page naming it, and the entry says so rather than naming one for ScraperAPI.

Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.

On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.

Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →