RealtyCrawl

RealtyCrawl is a real estate data service for developers, research teams, proptech applications, and AI workflows. It provides a shared way to search supported property listing sources and inspect property observations, while keeping the source context alongside the data. Applications can use the REST API directly, connect through the hosted MCP server, or install an agent skill that explains operation selection and request steps.
Responses are designed to preserve details that help teams interpret and audit property information. Depending on the selected source and operation, that context can include source identifiers and URLs, currency, price period, area units, observation time, request outcomes, and warnings. Null fields and partial results are not hidden; applications can distinguish unavailable information from a value that was returned. Asking prices, completed transactions, and modeled valuations are different types of evidence and should not be treated as interchangeable.
Developers can begin by discovering current capabilities for a requested source and country, reviewing the relevant operation contract, and then making a bounded request. Supported fields, filters, and operations vary by source. The public catalog includes research and documentation-backed beta coverage, so a catalog entry is not a guarantee that every operation is currently available. Documentation-backed beta status is not the same as fresh live verification. Check availability and the API documentation before building a workflow around a source.
The service is suited to teams adding listing search and property observations to an application, proptech products integrating source-labelled data, research teams retaining provenance behind comparisons, and agent builders connecting real estate workflows through REST or MCP. RealtyCrawl returns observations and request metadata; your application remains responsible for collection schedules, persistence, analysis, and alerts. Stored observations may represent an earlier collection rather than a currently available listing, so retain timestamps and verify details with the linked source when recency matters.
Integration options include REST, a hosted MCP endpoint, and an installable agent skill. Public source and capability discovery, an OpenAPI reference, examples, and reusable integration instructions help teams inspect the interface before making requests. Documented operations support request credit caps and idempotency. Authenticated data requests require a RealtyCrawl API key; use a placeholder in examples and keep keys private. Set an explicit credit budget and inspect request outcomes and any partial-result warnings.
Eligible new accounts receive 500 signup credits once for evaluation; this is not a recurring monthly free allowance. Advertised paid plans start at $15 per month, subject to billing and checkout availability. Monthly credits expire at the end of their billing period without rollover, while historical permanent balances and signup credits remain usable without subscribing. Requests stop when available credits are exhausted, with no automatic overage charges. Check the current pricing page and service documentation for up-to-date terms.