Balasar FeedProof — Product JSON-LD Check

Free beta for checking a shop you own or have explicit permission to inspect. Compare an exact SKU, price, currency and availability with static product JSON-LD. FeedProof reads public HTML; it does not open a browser, log in or change your shop. It does not verify visible prices, JavaScript-rendered variants, tax, checkout or legal compliance.

Start with the sample

Leave Synthetic sample enabled for an original, network-free example. This is labelled synthetic in the result. For a real check, disable it and enter the parameters below, replacing the placeholder URL and hostname with your permitted shop. Do not include secrets or personal data.

{
  "sample": false,
  "parameters": {
    "products": [{
      "sku": "0001",
      "url": "https://your-shop.example/item",
      "price": "12.50",
      "currency": "EUR",
      "availability": "in_stock"
    }],
    "allowedHosts": ["your-shop.example"],
    "allowedUseConfirmed": true
  }
}

SKU, price and currency must be strings. Keep leading SKU zeroes. Use a decimal point, a three-letter uppercase currency and in_stock, out_of_stock or preorder. Listing a hostname does not give permission to scrape it: check the source's terms and your rights first. Robots rules are checked before product pages; they do not replace permission. The publisher-permitted acceptance example used the fictional shop at https://magicscraper.app/demo/. The placeholder above is not a working integration.

Read the result

Open the run's Output tab or its default key-value store's OUTPUT record. Each product includes its SKU, URL, status and, where available, structured observations, differences, a timestamp, page hash and robots evidence. Page HTML is not saved by this Actor.

Result	Meaning
STRUCTURED_DATA_MATCH	One exact SKU and one unambiguous offer match the supplied fields.
MISMATCH	Observed structured fields differ; see the listed differences.
INDETERMINATE	The evidence is missing, inaccessible, ambiguous or unsupported. Neither a pass nor proof of a shop error.

CHECK_COMPLETE means all requested products received a result, not that all matched. Multiple offers, unclear variants, malformed JSON-LD and additional price specifications require manual checking. HTML comments, templates and non-HTML responses are not product evidence. JSON-LD graphs, product lists and explicit SKU-specific variants are supported conservatively.

Limits and costs

No Actor fee or paid event is enabled. Apify platform usage can consume your included credits or incur charges under your own Apify plan. This beta does not guarantee zero platform cost. Keep an account spending limit appropriate to your budget before running it.

A run accepts at most 20 products and five exact hostnames, with 25 HTTPS requests, 2 MiB per response, 10 MiB total response data and a 60-second network budget. The published default uses 256 MiB memory, a 90-second run timeout and no restart on error. Public IPv4 DNS addresses are pinned to each connection. Redirects, private network targets, IPv6-only sources and compressed responses are unsupported. Robots delays above ten seconds are declined; shorter delays must fit the run budget. Errors remain inconclusive; no bypass is attempted.

Privacy, retention and deletion

The Actor uses limited Apify permissions. It restricts each run and its default key-value store to authorized account access and verifies those settings before saving results. Making the Actor public does not make your results public. Account collaborators with granted access may read them. Input and results remain in Apify storage. This Actor sends no report to an external service, creates no named history store and logs static error codes rather than page content.

Retention is managed by Apify and your account plan. Unnamed run storage expires according to that policy; naming storage or changing sharing settings can change its retention or access. There is no separate automatic erasure service or fixed deletion guarantee from Balasar. To delete sooner, open Storage → Key-value stores in Apify Console and delete the run's store, then delete the run from Runs if you also want its metadata removed. Deletion is permanent. Do not change storage sharing to public or enter credentials in product URLs.

Support and beta scope

Use this Actor's Issues tab for support. Include the run ID, static error code and a redacted description of the expected result. Never post tokens, private inputs or customer data. Support is best effort, with no uptime or response-time guarantee. Recheck uncertain results manually before business decisions. Compatibility may change during the beta.

The runtime rejects live billing. A billable field is not a charge; chargedEvents is zero. This beta makes no revenue, conversion or checkout-accuracy promise. Third-party dependency notices are included in the source package as THIRD_PARTY_NOTICES.md.