One-call-one-scan API policy

An API usage rule tying each read request to a genuine user action such as scanning a product, deliberately steering bulk and research workloads toward the official dumps instead of the live endpoint.

In this catalog it appears concretely: - Open Beauty Facts API policy — "one call = one real scan by a user; scraping is discouraged because complete dumps are provided".

Access method sets your maintenance bill. Delivery routes change, layouts drift and scrapers rot quietly; whoever operates your pipeline inherits all of it, which is why access should be priced alongside the license itself.

The failure mode is concrete: a source can carry the One-call-one-scan API policy label while differing from what you need on exactly the dimension that matters — one call = one real scan by a user; scraping is discouraged because complete dumps are provided. Comparing two sources on that line usually settles the choice faster than any feature matrix.

You rarely have to take a vendor's word for it. 82.4% of the 1,744 datasets Datadory catalogs are free to access, and Open Beauty Facts API policy lets you inspect the real artifact before any budget is committed.

Treat every claim of this attribute as testable:

1. Open Open Beauty Facts API policy and confirm its record — "one call = one real scan by a user; scraping is discouraged because complete dumps are provided" — against the files you actually receive.
2. Pin down update cadence in writing. Across this catalog, 22.6% of 1,744 datasets refresh daily and 64 still arrive only through a manual request form, so ask exactly how fresh each release is.
3. Check whether definitions are verified at all. Field definitions are verified for 1495 of 1,744 datasets (85.7%), and any source you license should meet that bar.
4. Price the delivery route before the license. In this catalog bulk download is the most common access method (725 datasets) ahead of official APIs (574), and 379 sources still require scraping — a maintenance cost that lands on you, not the vendor.

See the term applied to real records: household-products data, personal-care-products data.

Adjacent concepts worth reading next: - bot mitigation - Nightly bulk dump - robots.txt crawl rules