chain-store-footprint-analysis
Chain store footprint analysis
Access and scope
Set CRAWLORA_API_KEY to your Crawlora key. Prefer the listed Crawlora MCP tools
when connected; otherwise use the bundled scripts/crawlora.sh, which sends
x-api-key to https://api.crawlora.net/api/v1. Read
reference/endpoints.md for exact methods and parameters.
Check application code as well as HTTP status; payloads are inside data.
Stop on authentication errors, back off on 429, and retry a transient upstream
failure once. Bound calls/pages by the requested scope and credit budget. Retain
source IDs, URLs, source dates, and observation/crawl times separately.
Map observed branches for specified chains and geographic boundaries. Establish brands/aliases, store versus kiosk/licensed location scope, cities or coordinate boundaries, amenity criteria, source set, and collection budget before counting. This describes observed supply, not sales, foot traffic, demand, or site profitability.