Source governance

Authorization is source-specific.

Public accessibility, robots.txt, an API endpoint, or an affiliate account does not by itself authorize collection or comparison.

Last updated September 22, 2026

WishWeeder does not use login automation, proxy rotation, CAPTCHA solving, stealth browsers, private APIs, or technical bypasses to obtain source content.

Permitted acquisition modes

  • Licensed feed governed by a publisher or advertiser agreement.
  • Public API whose documented terms permit the intended fields and use.
  • Approved HTTP or browser access only with source-specific permission and controls.
  • Manual observation where lawful and independently reviewed.
  • Disabled when rights, terms, market context, or technical refusal are unresolved.

Approval record

Before automation, each source and market must record:

  • the rights basis and applicable agreement or written permission;
  • the exact host, endpoint or feed, allowed fields, and market scope;
  • comparison, mobile, browser, free-tier, and paid-tier display rights;
  • retention, refresh, attribution, deep-link, and export obligations;
  • request limits, stable identity, refusal behavior, owner, and kill switch; and
  • termination, unpublishing, and deletion requirements.

Refusal and uncertainty

A 401, 403, 429, CAPTCHA, WAF challenge, robots denial, contract change, or uncertain authorization pauses acquisition. It does not trigger evasion. Missing permission keeps a source in review-required or prohibited state.

Current source position

Open Prices was used for a bounded food-price engineering spike under ODbL, but it does not satisfy the intended luxury catalog. WishWeeder is prioritizing an authorized retailer feed and will publish a source dossier before enabling one.