Source priority

  1. Official developer, product and help documentation
  2. Official company announcements and research with stated methodology
  3. Documentation from protocol or standards owners
  4. Secondary sources — for context only

Claim-source matching

If a source verifies that a capability exists, we do not infer market share, quality or entitlement from it. Partner-only or access-controlled documentation is labeled accordingly.

Change-sensitive information

API versions, endpoints, authentication, quotas, commercial models, eligibility and pricing are kept close to their sources and tied to a review date. Unsourced quota, CPC or access claims are not published.

Reports

Population, geography, time window, methodology and limitations are kept visible whenever possible. Survey intent is not presented as if it were observed booking behavior.

Broken and inaccessible sources

Definite 404/410 responses are treated as broken and replaced or removed. Automated-access responses such as 401/403/429 do not by themselves invalidate a source; where possible they are supplemented with a current public official surface.