Tabelog Japan Restaurant Budget & Scores by Area

What it does: Reads Tabelog (Japan's largest restaurant review site) and returns one summary per area: restaurant count, budgets, score spread, top genres and stations.

You enter: Tabelog area paths (or URLs), e.g. tokyo/A1301/A130101 = Ginza. Optional genre like sushi.

You get: One row per area: how many restaurants it lists; from 60 sampled across it: dinner/lunch budget bands with a median, score median, range and share that have a score, top genres and stations. Optional: one row per restaurant, plus address, phone, coordinates.

Price: $0.02 per area, up to 10 areas per run, each charged. +$0.002 per restaurant if you also want each restaurant, +$0.002 per restaurant detail page (address, phone, coordinates); both off by default. No results = no charge.

Example: enter tokyo/A1301/A130101 (Ginza) → 2,670 restaurants listed; measured on 60 sampled across the area (pages 1, 31, 60): dinner median band ¥6,000–7,999 · lunch median band ¥2,000–2,999 · score median 3.47 (range 3.26–4.61) · top genre Japanese Cuisine (12 of the 60) (real run, 2026-08-17)

Unofficial — not affiliated with Tabelog. Reads public pages only.

Input

Field	Example	Notes
areas	["tokyo/A1301/A130101"]	Area path <prefecture>/<large area>/<medium area>. A full https://tabelog.com/... URL works too and is normalised down to the area path. 1–10 areas per run — each area is a separate billable unit ($0.02 each) and its own set of requests 2 s apart, so keeping runs short is what keeps them inside the 300 s timeout. Split a bigger job into several runs
genre	"sushi"	Optional genre slug, used as a path segment: sushi, ramen, izakaya, yakitori, washoku, japanese, seafood, soba, unagi, okonomiyaki, monjya, yoshoku, … Empty = all genres
sort	"rating"	rating (点数の高い順, SrtT=rt) / most-viewed / most-reserved / standard. Newest-first is not offered — see the note below
pagesPerArea	3	20 restaurants per page, 1–10 pages. 3 pages = up to 60 restaurants
includeIndividualItems	false	Off by default. Enable to also get one record per sampled restaurant (+$0.002 each)
fetchDetails	false	Off by default. Enable to also read each restaurant's own page and add address / phone / lat-lng / seats / hours (+$0.002 each)
maxDetails	10	How many detail pages per area (1–20). One extra request, 2 s apart, per restaurant

Finding an area code: open the area on Tabelog and copy the URL — all three parts are needed (<prefecture>/<large area>/<medium area>), and pasting the whole URL into areas works. Measured 2026-08-18: tokyo/A1301/A130101 Ginza (2,670 restaurants), tokyo/A1303/A130301 Shibuya (3,614), tokyo/A1304/A130401 Shinjuku (5,568), osaka/A2701/A270101 Osaka Station & Umeda (6,917). A two-part path such as tokyo/A1303 is rejected before any request, and a medium-area code Tabelog does not know fails the area instead of being charged — see the note below.

Output

One type: "area_summary" record per area:

Measured on 2026-08-17 (real run, tokyo/A1301/A130101 = Ginza, default settings) — the complete record that run wrote, nothing removed, plus the areaStatus field added on 2026-08-18 (that run predates it).

{
  "type": "area_summary",
  "area": "tokyo/A1301/A130101",
  "areaUrl": "https://tabelog.com/en/tokyo/A1301/A130101/rstLst/?SrtT=rt",
  "genre": null,
  "sort": "rating",
  "areaStatus": "ok",
  "totalRestaurantsFound": 2670,
  "totalListingsFound": 2670,
  "sampledRestaurants": 60,
  "pagesFetched": 3,
  "sampledPages": [1, 31, 60],
  "enumerablePages": 60,
  "sourceLocale": "en",
  "tabelogScore": {"min": 3.26, "p25": 3.27, "median": 3.47, "p75": 4.15, "max": 4.61, "average": 3.68},
  "scoredShare": 1.0,
  "reviewCount": {"min": 33, "p25": 157, "median": 382, "p75": 462, "max": 1620, "average": 395},
  "reviewCountKnown": 60,
  "distanceMeters": {"min": 29, "p25": 147, "median": 190, "p75": 263, "max": 481, "average": 210},
  "distanceMetersKnown": 58,
  "genreTop": [["Japanese Cuisine", 12], ["French", 7], ["Sushi", 6], ["Dining bar", 6], ["Izakaya (Japanese style tavern)", 6], ["Steak", 5], ["Italian", 5], ["Cafe", 5], ["Shabu shabu (Japanese hotpot)", 4], ["Seafood", 4]],
  "stationTop": [["Ginza Sta.", 30], ["Ginza Itchome Sta.", 14], ["Higashi Ginza Sta.", 13], ["Shimbashi Sta.", 1]],
  "detailsFetched": 0,
  "checkedAt": "2026-08-17T17:44:12.743374+00:00",
  "sourceUrl": "https://tabelog.com/en/tokyo/A1301/A130101/rstLst/?SrtT=rt",
  "dinnerBudgetBands": [{"band": "-JPY999", "count": 3}, {"band": "JPY1,000-JPY1,999", "count": 4}, {"band": "JPY2,000-JPY2,999", "count": 3}, {"band": "JPY3,000-JPY3,999", "count": 2}, {"band": "JPY4,000-JPY4,999", "count": 2}, {"band": "JPY5,000-JPY5,999", "count": 4}, {"band": "JPY6,000-JPY7,999", "count": 11}, {"band": "JPY8,000-JPY9,999", "count": 3}, {"band": "JPY10,000-JPY14,999", "count": 2}, {"band": "JPY15,000-JPY19,999", "count": 2}, {"band": "JPY20,000-JPY29,999", "count": 1}, {"band": "JPY30,000-JPY39,999", "count": 3}, {"band": "JPY40,000-JPY49,999", "count": 6}, {"band": "JPY50,000-JPY59,999", "count": 5}, {"band": "JPY60,000-JPY79,999", "count": 3}, {"band": "JPY80,000-JPY99,999", "count": 1}, {"band": "JPY100,000-", "count": 1}],
  "dinnerBudgetMedianBand": "JPY6,000-JPY7,999",
  "dinnerBudgetP25Band": "JPY5,000-JPY5,999",
  "dinnerBudgetP75Band": "JPY40,000-JPY49,999",
  "dinnerBudgetLowerJpy": {"min": 1000, "p25": 5000, "median": 8000, "p75": 40000, "max": 100000, "average": 21585},
  "dinnerBudgetUpperJpy": {"min": 999, "p25": 5499, "median": 7999, "p75": 49999, "max": 99999, "average": 24363},
  "lunchBudgetBands": [{"band": "-JPY999", "count": 5}, {"band": "JPY1,000-JPY1,999", "count": 9}, {"band": "JPY2,000-JPY2,999", "count": 7}, {"band": "JPY3,000-JPY3,999", "count": 5}, {"band": "JPY5,000-JPY5,999", "count": 2}, {"band": "JPY10,000-JPY14,999", "count": 3}, {"band": "JPY15,000-JPY19,999", "count": 2}, {"band": "JPY20,000-JPY29,999", "count": 3}, {"band": "JPY40,000-JPY49,999", "count": 4}, {"band": "JPY50,000-JPY59,999", "count": 1}],
  "lunchBudgetMedianBand": "JPY2,000-JPY2,999",
  "lunchBudgetP25Band": "JPY1,000-JPY1,999",
  "lunchBudgetP75Band": "JPY10,000-JPY14,999",
  "lunchBudgetLowerJpy": {"min": 1000, "p25": 1750, "median": 3000, "p75": 15000, "max": 50000, "average": 10500},
  "lunchBudgetUpperJpy": {"min": 999, "p25": 1999, "median": 2999, "p75": 14999, "max": 59999, "average": 12462}
}

Reading the statistics — every one of them states its denominator. sampledRestaurants is the whole sample; the three fields next to it say how much of that sample each distribution actually covers, because Tabelog leaves these fields blank on many cassettes:

Field	Denominator for	Means
scoredShare	tabelogScore	Share (0–1) of the sampled restaurants that carry a Tabelog score at all — the rest render 「-」
reviewCountKnown	reviewCount	Count of sampled restaurants whose cassette states a review count
distanceMetersKnown	distanceMeters	Count of sampled restaurants whose cassette states a walking distance from a station

So distanceMeters.median with distanceMetersKnown: 58 and sampledRestaurants: 60 — as in the record above — is the median over 58 restaurants, not 60. pagesFetched plays the same role for sampledRestaurants itself, and a run cut short by the time budget also carries truncatedForTimeLimit: true.

With includeIndividualItems: true, one type: "restaurant" record per sampled restaurant:

Example values (shape only — numbers are illustrative).

{
  "type": "restaurant",
  "area": "tokyo/A1301/A130101",
  "tabelogId": "13108000",
  "name": "おたる政寿司 銀座",
  "url": "https://tabelog.com/tokyo/A1301/A130101/13108000/",
  "score": 3.47,
  "reviewCount": 596,
  "station": "銀座一丁目駅",
  "distanceMeters": 62,
  "genres": ["寿司", "日本料理", "海鮮"],
  "dinnerBudgetBand": "￥15,000～￥19,999",
  "lunchBudgetBand": "￥4,000～￥4,999"
}

With fetchDetails: true, one type: "restaurant_detail" record for the first maxDetails restaurants — the same fields plus address, postalCode, addressRegion, addressLocality, streetAddress, telephone, latitude, longitude, priceRange, servesCuisine, seats, openingHours, reservationPolicy, transport.

Pricing — $0.02 per area

Event	Price	When
Area market summary (area-analyzed)	$0.02	Per area analyzed
Individual restaurant (restaurant-scraped)	$0.002	Only if you enable Include individual restaurants
Restaurant detail record (restaurant-detail-scraped)	$0.002	Only if you enable Fetch restaurant detail pages

Individual restaurant records and detail records are OFF by default, so a default run (1 area, 3 pages, summary only) costs a flat $0.02 and takes about 6 seconds. You pay per area you enter; there is no monthly fee. An area that returns zero restaurants is never charged. A search Tabelog itself answers with zero restaurants (a real genre with nothing in that area) returns a free, empty summary marked areaStatus: "no_listings"; an area path or a genre slug Tabelog does not recognise fails the area instead, so a typo never comes back as a plausible-looking number. Both checks read what the page itself says was applied — the breadcrumb trail for the area, the filter chips for the genre — not the URL that was requested.

Notes & limits

• The numbers come from Tabelog's English edition (/en/), and so do the strings. Restaurant names, genres and station names are returned in English, and a budget band reads JPY8,000-JPY9,999. The ids, scores, review counts and prices are the same values the Japanese site serves — verified page by page (pages 1, 10 and 60 return identical restaurant ids and identical scores under sort: "rating"). Every summary states this as sourceLocale. The reason is transport, not preference: since 2026-08-03 Tabelog's Japanese listing path answers a Cloudflare challenge to datacenter IPs, while the localized paths do not
• Review text is never collected. Review bodies, reviewer names, reviewer page links and review photos are never parsed, stored or emitted. Every field is read out of the one element that carries its own class token, so review text cannot leak into a record even by accident. Review counts (a number) are included
• The default order is rating (SrtT=rt), and newest-first is not offered. standard is Tabelog's own editorial "recommended for visitors" order and is ad/PR weighted — the same trap as SUUMO's おすすめ順 — so it is never the default. Newest-first (新着順) is not offered at all: the pages this Actor reads ignore that parameter and answer with the editorial order, so a sample labelled newest would not actually be in that order. Every record states the sort it was produced with
• The sample is a sample, and it is spread — not taken off the top. totalRestaurantsFound is the whole area; sampledRestaurants is what the statistics are computed on (pagesPerArea × 20). Because the sort is monotonic in score, the first pages are the highest-rated restaurants, so the pages are spread across the whole result set instead: 3 pages of a 2,666-restaurant area are pages 1, 31 and 60. sampledPages says exactly which ones were used. Raise pagesPerArea for a finer distribution
• Tabelog stops enumerating a result set at page 60 / 1,200 restaurants, whatever the hit count says (measured on a 2,666-restaurant area and a 5,560-restaurant area alike). totalRestaurantsFound is still how many the area really lists, and enumerablePages says how much of that can be walked through; areas larger than that must be sliced with genre to be enumerated exhaustively
• scoredShare, reviewCountKnown and distanceMetersKnown matter. A large share of Tabelog restaurants have no score, no review count or no station distance at all. tabelogScore covers only the scored ones, reviewCount only the ones with a count and distanceMeters only the ones with a distance — and each of the three says exactly how many that was, against sampledRestaurants
• A list page is 20 cassettes, and some of them are ads. PR/ad cassettes carry no restaurant link, so a full page can yield 19 records. The page loop counts cassettes, not records, when it decides whether it has reached the end of the area — otherwise a single ad on page 1 would end the run one page in
• areaStatus says which kind of answer you got: ok when restaurants were sampled, no_listings when Tabelog answered for exactly this area and listed none. A no_listings record also carries a one-line hint with the next thing to try, in its own field — never mixed into the statistics — and is not charged either way
• The hit count is live and drifts by a few between requests, so totalRestaurantsFound is a snapshot, not a stable key
• An unknown area code does not 404 on Tabelog either — it answers with the area above the one you asked for. Measured 2026-08-18: tokyo/A9999/A999999 comes back with all 139,210 restaurants in Tokyo, and tokyo/A1301/A130199 with all 6,257 in the Ginza large area, both under the path that was requested. The run compares the page's breadcrumb trail with the area asked for and fails the area when Tabelog answered for a wider one, so a mistyped code is never billed as that area's market
• An unknown genre slug does not 404 on Tabelog — it is silently dropped and the page comes back with the whole area (measured: mexico in a 1,602-restaurant area returns all 1,602). Tabelog echoes each filter it applied back on the page, and the area fails when the genre is not among them, rather than billing you for area-wide numbers labelled as a genre
• Tabelog's "broaden your search" shelf is never counted as a result. When a search returns few hits, Tabelog appends a second list of restaurants from a wider search under 「Changing your filter may help you find more restaurants」, in identical markup (measured: a 1-hit search renders 11 restaurant cards, a 2-hit search 12). Those cards are cut before parsing, so sampledRestaurants only ever counts restaurants that actually matched
• Read-only and throttled (1 request / 2.0 s). A run has a 95-second soft budget and areas is capped at 10, which is what keeps a worst case inside the Actor's 300-second timeout. Page 1 of every area always runs, so every area produces a record; the follow-up list pages and the detail-page enrichment are what get skipped once the budget is spent, and the affected summary keeps what it collected and carries truncatedForTimeLimit: true with a smaller pagesFetched
• If every area fails, the run fails — never a silent empty success
• No personal data. Restaurant business information only: name, address, phone, coordinates, seats, hours. No reviewers, no customers

Use cases

• B2B lead lists for the restaurant industry — POS, reservation SaaS, food wholesale, payments: pull an area, filter by budget band and genre, enrich the top N with address and phone
• Site selection & competitive density — how many sushi restaurants are within 300 m of this station, and at what price point
• Price positioning — what dinner budget band the neighbourhood actually sits in before you set your own menu prices
• Market monitoring — schedule the Actor per area and track the median band, the score distribution and the restaurant count over time
• Inbound-tourism and delivery planning — genre mix and budget mix per station area

---

日本語ガイド

食べログのエリア相場を、エリア1件につき1レコードで返す Actor です。

• 概要: エリア(<都道府県>/<大エリア>/<小エリア>、例 tokyo/A1301/A130101 = 銀座)を指定すると、そのエリアの掲載店舗数・夜/昼の予算帯分布・食べログ点数の分布・口コミ件数の分布・ジャンル構成・最寄駅構成・駅からの距離を1レコードで返します。予算帯は食べログの帯(～￥999〜￥30,000～)をそのまま安い順に並べ、中央値の帯(帯は順序尺度なので平均ではなく順位の中央値)と帯の上限/下限の円建て統計を併せて返します。
• 点数の扱い: 食べログは点数の付いていない店が多数あります。tabelogScore は点数のある店だけの分布で、scoredShare がその割合です(点数無しの店を黙って落とした分布は嘘になるため必ず併記します)。同様に reviewCount には reviewCountKnown、distanceMeters には distanceMetersKnown(いずれも「その統計に実際に寄与した店舗数」)を必ず併記します。分母は sampledRestaurants です。
• 使い方: areas にエリアパスを入れます。食べログの URL をそのまま貼っても構いません(自動で正規化します)。genre でジャンルを絞れます(sushi / ramen / izakaya など、URL のパスセグメントと同じスラッグ)。個別店舗のレコードが必要なときだけ includeIndividualItems、住所・電話・緯度経度・席数・営業時間まで必要なときだけ fetchDetails を ON にします。
• 料金: エリアサマリー1件 $0.02、個別店舗レコード $0.002/件、詳細レコード $0.002/件。個別レコードと詳細取得は既定 OFF なので既定実行は $0.02 固定です。0件のエリアには課金されません。 食べログ自身が0件と答えた検索(実在するジャンルだが、そのエリアには無い)は空のサマリーを無料で返します(areaStatus: "no_listings" と次の一手の hint 付き)。食べログが知らないエリアコード/ジャンルスラッグは404 にならず「ひとつ上のエリア」の結果が返ってくるため(実測: tokyo/A9999/A999999 は東京都全体の 139,210 件)、ページ自身が示すパンくず(エリア)と適用条件チップ(ジャンル)を照合し、要求と違うものが返っていればそのエリアを失敗として扱います。打ち間違いがもっともらしい数字になって課金されることはありません。なお、ヒットが少ないときに食べログが付け足す「条件を広げた候補」の店舗はサンプルに入れません(1件ヒットの検索に11枚のカードが並ぶことを実測)。
• 数値も文字列も食べログの英語版(/en/)から取得しています。 店名・ジャンル・駅名は英語で返り、予算帯は JPY8,000-JPY9,999 の表記になります。ID・点数・口コミ件数・価格は日本語サイトと同一の値です(sort: "rating" で1・10・60ページを突き合わせ、店舗IDと点数が完全一致することを確認済み)。各サマリーに sourceLocale として明記されます。理由は好みではなく経路です — 2026-08-03 以降、食べログの日本語一覧パスはデータセンターIPに対して Cloudflare のチャレンジを返すのに対し、多言語版パスは返さないためです
• 並び順の注意: standard は食べログの編集推薦順 = 広告/PR 加重順です(SUUMO のおすすめ順と同型の罠)。そのため既定は rating(点数の高い順 = SrtT=rt) です。新着順は提供しません — 本 Actor が読むページはそのパラメータを無視して編集推薦順を返すため、newest と名乗ると取得順を偽ることになります。どの並び順で取得したかは全レコードの sort に必ず記録されます。
• 口コミ本文は一切取得しません。 口コミ本文・投稿者名・投稿者ページへのリンク・口コミ写真は、パースも保存も出力もしません。取得するのは店舗の事業所情報のみで、口コミは件数(数値)だけを扱います。
• 上限: 1ページ20件で、掲載件数がいくつであっても列挙は60ページ(1,200件)で止まります(2,666件のエリアでも5,560件のエリアでも同じことを実測)。母数 totalRestaurantsFound はエリアの実数のまま、歩ける深さは enumerablePages に出ます。全件を数え上げたい場合は genre で分割してください。サンプルは先頭から連続では取らず、結果集合全体に散らして取ります(並び順が点数について単調なため、先頭ページは高得点店ばかりでエリアの分布にならない)。2,666件のエリアで3ページなら実際に取るのは1・31・60ページで、sampledPages に明記されます。リクエスト間隔は 2.0 秒固定です。areas は1回の実行につき最大10件(1件ごとに課金・リクエストが増えるため)。実行時間の上限に達した場合は、以降のリストページ取得を打ち切り、取得済みの分でサマリーを返して truncatedForTimeLimit: true と実際の pagesFetched を記録します(各エリアの1ページ目は必ず取得します)。

---

中文指南

日本最大的餐厅点评网站「食べログ(Tabelog)」的商圈行情，一次调用返回一条汇总记录。

• 功能: 指定商圈(<都道府県>/<大区>/<小区>，例如 tokyo/A1301/A130101 = 银座)，即可获得该商圈的餐厅总数、晚餐/午餐预算区间分布、Tabelog 评分分布、点评数量分布、菜系构成、最近车站构成与步行距离。预算区间按食べログ原始档位(～￥999 至 ￥30,000～)由低到高排列，并给出中位数档位(档位是序数，因此取排名中位数而非平均值)与档位上下限的日元统计。
• 评分说明: 食べログ上有大量餐厅没有评分。tabelogScore 仅统计有评分的餐厅，scoredShare 表示其占比 —— 悄悄丢弃无评分餐厅的分布是不诚实的。同理，reviewCount 配 reviewCountKnown、distanceMeters 配 distanceMetersKnown(均为实际参与该统计的餐厅数量)，分母为 sampledRestaurants，让每项统计都有明确的覆盖范围。
• 用法: 在 areas 中填入商圈路径，直接粘贴完整的食べログ网址也可以(会自动规范化)。用 genre 限定菜系(sushi / ramen / izakaya 等，与网址中的路径段一致)。需要单店记录时开启 includeIndividualItems；需要地址、电话、经纬度、座位数、营业时间时开启 fetchDetails。
• 价格: 商圈汇总每条 $0.02，单店记录每条 $0.002，详情记录每条 $0.002。单店记录与详情抓取默认关闭，因此默认运行固定为 $0.02。零结果的商圈不收费。 食べログ自身回答为 0 家的检索(菜系存在、但该商圈没有)会免费返回一条空汇总(标记 areaStatus: "no_listings" 并附一句 hint)；食べログ无法识别的商圈代码或菜系 slug 不会返回 404，而是返回「上一级商圈」的结果(实测: tokyo/A9999/A999999 返回东京都全部 139,210 家)，因此本 Actor 会核对页面自身的面包屑(商圈)与已应用条件标签(菜系)，与请求不符时判定该商圈失败，拼写错误不会变成一个看似合理的数字并被计费。另外，命中数很少时食べログ会追加「放宽条件后的推荐」餐厅，这些不计入样本(实测:命中 1 家的检索会渲染 11 张餐厅卡片)。
• 数值和文字都取自食べログ的英文版(/en/)。 店名、菜系、车站名会以英文返回，预算档位写作 JPY8,000-JPY9,999。ID、评分、点评数与价格与日文站完全相同（在 sort: "rating" 下逐页比对第 1、10、60 页，店铺 ID 与评分完全一致）。每条汇总都会用 sourceLocale 写明这一点。原因是通道而非偏好：自 2026-08-03 起，食べログ的日文列表路径会对数据中心 IP 返回 Cloudflare 验证，而多语言版路径不会
• 排序提醒: standard 是食べログ的编辑推荐顺序，带广告/推广加权，因此不作默认。默认是 rating（评分从高到低 = SrtT=rt）。不提供最新开业顺序 —— 本 Actor 读取的页面会忽略该参数并改用编辑推荐顺序，标成 newest 就等于谎报取样顺序。每条记录都会记录实际使用的 sort。
• 绝不采集点评正文。 点评正文、点评人昵称、点评人主页链接与点评照片一律不解析、不存储、不输出，只采集餐厅的经营信息；点评仅使用数量(数字)。
• 上限: 每页 20 家，无论命中数是多少，枚举都只到第 60 页(1,200 家)（在 2,666 家和 5,560 家的商圈上分别实测，结果一致）。母数 totalRestaurantsFound 仍是商圈实际数量，可枚举深度记在 enumerablePages。需要穷举时请用 genre 拆分。取样不是从头部连着取，而是散布在整个结果集上（排序对评分单调，头几页全是高分店，不能代表商圈）。2,666 家的商圈取 3 页时实际取的是第 1、31、60 页，并写入 sampledPages。请求间隔固定 2.0 秒。每次运行最多 10 个 areas(每个商圈单独计费、单独发起请求)。达到运行时间预算后将停止抓取后续列表页，用已获取的数据生成汇总并标记 truncatedForTimeLimit: true(pagesFetched 如实记录)；每个商圈的第 1 页始终会抓取。

If something goes wrong

• Wrong number or a failed run? Open a ticket on the Issues tab. I read every one and reply within 2 business days (Japan time).
• You never get a fake "empty" result. If the site can't be read, the run fails and says so.
• No results = no charge. You only pay for results you actually get.
• Checked every week. An automatic test runs this tool weekly; if the site changes, I fix it.
• Public pages only. No login, no personal data, and it goes easy on the site.

More tools by the same author

• Mercari Japan Sold Prices — What Items Really Sell For
• Yahoo! Auctions Japan Sold Prices — Median, Range, Bids

Other language editions of this tool: 中文 · 한국어

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): https://apify.com/jpmarketdata

Disclaimer

Unofficial, independent tool — not affiliated with, endorsed by, or sponsored by Tabelog. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.