Listing search monitoring
Redfinエンドポイントを使えば、「Listing search monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Use a Redfin API to turn public Redfin listing search, property detail, Redfin Estimate, comparables, and regional market-trend pages into structured JSON for real estate research, valuation, and market-monitoring workflows.
Use a Redfin API to collect listing search, property detail, Redfin Estimate, and regional market-trend data as structured JSON for real estate intelligence.
エンドポイントファミリー
5
ドキュメント化されたパラメータ
21
サンプル数
5
ライブカタログスナップショット
稼働エンドポイント
5
メソッド
GET
必須パラメータ
8
スキーマ参照
5
{
"platform": "Redfin",
"endpoint": "redfin-search",
"method": "GET",
"path": "/redfin/search",
"auth": "apiKey"
}無料ツール
ユースケース
Use a Redfin API to collect listing search, property detail, Redfin Estimate, and regional market-trend data as structured JSON for real estate intelligence.
Redfinエンドポイントを使えば、「Listing search monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Redfinエンドポイントを使えば、「Property valuation with Redfin Estimate」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Redfinエンドポイントを使えば、「Regional market trend analysis」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のRedfinエンドポイントカタログから取得しています（エンドポイント5件、ドキュメント化されたリクエストパラメータ21個、公開レスポンススキーマ5件）。DocsとPlaygroundが参照しているカタログと同じものです。
Redfinのエンドポイントは5件、5つのリクエストファミリーに分類されています（Estimate、Property、Region Trendsほか2件）。
これらのRedfinエンドポイントには21個のリクエストパラメータがドキュメント化されており、うち8個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
5件のRedfinエンドポイントのうち5件が実際のサンプルレスポンスを、5件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Redfinのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Redfinのエンドポイントは5個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/redfin/estimate
/redfin/property
/redfin/region-trends
/redfin/search
/redfin/similar
エンドポイントカタログ
/redfin/estimateReturns the Redfin Estimate for a property, including the current estimate, property facts, and the monthly estimate history with city/county/postal comparatives. Faithful pass-through of Redfin's public avm + avmHistoricalData resources.
MCPツール redfin_estimate
/redfin/propertyReturns Redfin public property details. Provide a listing url, or a property_id (optionally with listing_id).
MCPツール redfin_property
/redfin/region-trendsReturns Redfin's aggregate market trends for a region (median list/sale price, sale-to-list, offers, days on market, inventory, year-over-year). Faithful pass-through of Redfin's public aggregate-trends resource.
MCPツール redfin_region_trends
/redfin/searchReturns Redfin public listing search results. Pass region_id/region_type from autocomplete to skip location resolution.
MCPツール redfin_search
/redfin/similarReturns the comparable listings Redfin shows for a property, identified by the required `property_id`. Each row has the address, city, state, zip, price, beds, baths, `sqft`, `price_per_sqft`, days on market, MLS number, `hoa_monthly`, lot size, year built, status, image and URL, plus coordinates when present.
MCPツール redfin_similar
関連API
Real Estate & Property
Use a Zillow API to turn public property search, home detail, and location autocomplete pages into structured JSON for real estate research, market monitoring, and property intelligence workflows.
Real Estate & Property
Turn Rightmove — the UK's largest property portal — into structured JSON: location autocomplete, for-sale/to-let/sold property search with price and bedroom filters, dedicated commercial, new-homes and student-accommodation searches, estate-agent branch listings, and full property detail including floor plans, EPC rating, and nearby schools, all with one API key.
Real Estate & Property
Research Greystar's public rental communities and their location, floor-plan, fee, and available-unit records alongside local guides, renter resources, and corporate newsroom content.
Redfinのスクレイピング方法
Redfin property data complements Zillow for real-estate intelligence. Crawlora's Redfin endpoints return search, property, and estimate data as structured JSON. Redfin's five routes resolve places and properties through ids, and the documentation explains how to skip location resolution and what each pass-through returns. A pull on 2026-10-27 showed that Redfin region ids are its own: Zillow's Seattle id 16037 resolved to a single listing in Persia, Iowa on Redfin.
/redfin/property takes a listing url, or a property_id with an optional listing_id. /redfin/estimate takes a property_id and returns the current Redfin Estimate with property facts and monthly estimate history.
/redfin/similar takes a property_id and returns the comparable listings Redfin shows, each with address, city, state, zip and price. /redfin/region-trends takes region_id and region_type and returns median list and sale price, sale-to-list, offers, days on market, inventory and year-over-year change.
search resolves a display location through autocomplete unless you pass region_id, and region_type defaults to 6 (city). Pass the id and type from autocomplete to avoid the extra step, and use status for_sale or sold.
The property route takes a listing URL as its primary key, or a property_id with an optional listing_id that improves completeness. estimate and similar take property_id only.
estimate returns the current Redfin Estimate with property facts and monthly estimate history with city, county and ZIP comparatives, and region-trends returns median list and sale price, sale-to-list, offers, days on market, inventory and year-over-year change. similar returns comparable listings with address, price, beds, baths, sqft, price per sqft, MLS number and HOA.
search with region_id 16037 and region_type 6 returned one result in Persia, IA, not Seattle. Let search resolve the location, or take the id from Redfin itself, and keep the provider with every stored id.
The same route answered a later request with a request-budget error, so back off and retry rather than treating it as no results.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Redfin のデータを JSON として取得できます。Redfin に対応するスキル:
Compare US housing markets through Crawlora's historical housing dataset and Redfin tools. Use for city, metro, county, or ZIP-code comparisons of…
npx skills add github.com/Crawlora-org/crawlora-skills --skill housing-market-researchResearches homes and used cars via the Crawlora API — Zillow and Redfin property search/estimates/market trends, plus CarMax, Autotrader, and…
npx skills add github.com/Crawlora-org/crawlora-skills --skill real-estate-autos-researchFAQ
Send a Redfin region search or property URL to Crawlora's Redfin endpoint and get structured JSON — price, beds/baths, sqft, status, Redfin Estimate, history — without rotating proxies. Collect public data and respect Redfin's terms.
Yes — Crawlora returns both Redfin and Zillow in a normalized shape, so you can cross-reference listings, estimates, and history for the same property across sources.
Collecting publicly visible listing data is generally permissible if you respect Redfin's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.
No. Redfin does not offer a public API, self-serve API keys, or per-property REST endpoints for developers — its official Data Center provides only aggregate regional market-trend CSV downloads, not individual listing or property records. Crawlora's Redfin endpoints return per-property listing search, detail, Redfin Estimate, and market-trend data as structured JSON with a single API key.
6, which is a city. Pass region_type with region_id for a neighborhood, ZIP code or county.
estimate and similar require property_id. The property route accepts a listing URL instead.
No. On 2026-10-27 Zillow's id 16037 returned a listing in Persia, Iowa on Redfin.