Retail Price Proof — Retail price checks with page evidence
Pricing
$5.00 / 1,000 verified product checks
Retail Price Proof — Retail price checks with page evidence
Compare public product-page prices with your stated MAP threshold. Inspect price, currency and source evidence before acting on a finding. Demo: https://market-data-gateway-production-2084.up.railway.app/launch/retail-price-proof
Pricing
$5.00 / 1,000 verified product checks
Rating
0.0
(0)
Developer
Hadi Kanj
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Security
Limited permissionsShare
Retail Price Proof — Prices, Stock & MAP Checks
Check supplied public product URLs for advertised prices, currency and stock, with source-field evidence. Optionally compare prices with your own minimum advertised price (MAP). Use the same monitoring list name on repeated runs to track changes.
Quick start
Paste one to 100 product URLs into the input, then run:
{"products": [{"url": "https://nalgene.com/product/32oz-wide-mouth-bottle/"}],"stateKey": "my-products","onlyViolations": false}
For a threshold comparison, provide mapPrice and its three-letter currency together. Add sku to select a particular variant. Labels such as brand, seller and label are optional.
Output
Every check has a status, URL and check timestamp. Successful rows include lowestPrice, currency, stock where available, and evidence naming the captured source fields and URLs. Optional data remains null when unavailable. VERIFIED means an exact structured advertised price was extracted; it is not proof of a policy violation or a shopper's final checkout price.
Repeat a run with the same stateKey to compare price and stock changes. Configure an Apify Task and Schedule for recurring checks. The SUMMARY key-value-store record contains checked, verified, error and output counts. Export results as JSON or CSV. With onlyViolations enabled, successful non-violations are omitted; unsuccessful checks remain visible.
Blocked pages, robots exclusions, missing prices, unsupported SKUs and conflicting currencies/prices produce explicit statuses. Inspect each row even when the run succeeds.
Call from your application
Use your own Apify token in an Authorization header:
curl -X POST 'https://api.apify.com/v2/actors/6TTbl6Zm3BWZDLb9O/run-sync-get-dataset-items' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"products":[{"url":"https://nalgene.com/product/32oz-wide-mouth-bottle/"}],"stateKey":"my-products"}'
For longer runs, start asynchronously with POST /v2/actors/6TTbl6Zm3BWZDLb9O/runs, wait for completion and retrieve the returned default dataset. Keep tokens out of URLs and shared examples.
Scope and limitations
This tool checks URLs you supply. It does not discover all resellers, bypass access controls, interpret coupons, normalize country-specific shopper pricing, or determine whether a brand policy legally applies. Pages requiring browser interaction may be unsupported. Manually verify shopper-visible prices before enforcement. Stock is null when reliable availability evidence is absent. A page hash is included where available; this beta does not retain full pages or screenshots.
Support
Open an issue on the Actor's Issues tab with a public product URL, run ID and expected behavior. Never include credentials or private customer data.