Search where properties are listed
Search a location on a chosen source or combine supported sources in one request. Keep each result’s origin and check which sources completed.
Choose a search sourceExplore real estate source coverage
One property API. Real estate, unified.
A catalog of 200 researched real estate sources to explore, documented requests to test, and credits you can track. Check each operation’s availability during preview.
43 operations - 200 researched platforms - 100 free credits
import requests
# Check current source availability before collecting.
response = requests.get(
'https://realtycrawl.dev/v1/meta/capabilities',
params={'platform': 'zillow'}
)
response.raise_for_status()
capabilities = response.json()// Check current source availability before collecting.
const response = await fetch(
'https://realtycrawl.dev/v1/meta/capabilities?platform=zillow'
);
if (!response.ok) throw new Error('Request failed');
const capabilities = await response.json();curl 'https://realtycrawl.dev/v1/meta/capabilities?platform=zillow'import requests
# Check current source availability before collecting.
response = requests.get(
'https://realtycrawl.dev/v1/meta/capabilities',
params={'platform': 'redfin'}
)
response.raise_for_status()
capabilities = response.json()// Check current source availability before collecting.
const response = await fetch(
'https://realtycrawl.dev/v1/meta/capabilities?platform=redfin'
);
if (!response.ok) throw new Error('Request failed');
const capabilities = await response.json();curl 'https://realtycrawl.dev/v1/meta/capabilities?platform=redfin'import requests
# Check current source availability before collecting.
response = requests.get(
'https://realtycrawl.dev/v1/meta/capabilities',
params={'platform': 'realtor'}
)
response.raise_for_status()
capabilities = response.json()// Check current source availability before collecting.
const response = await fetch(
'https://realtycrawl.dev/v1/meta/capabilities?platform=realtor'
);
if (!response.ok) throw new Error('Request failed');
const capabilities = await response.json();curl 'https://realtycrawl.dev/v1/meta/capabilities?platform=realtor'import requests
# Check current source availability before collecting.
response = requests.get(
'https://realtycrawl.dev/v1/meta/capabilities',
params={'platform': 'rightmove'}
)
response.raise_for_status()
capabilities = response.json()// Check current source availability before collecting.
const response = await fetch(
'https://realtycrawl.dev/v1/meta/capabilities?platform=rightmove'
);
if (!response.ok) throw new Error('Request failed');
const capabilities = await response.json();curl 'https://realtycrawl.dev/v1/meta/capabilities?platform=rightmove'import requests
# Check current source availability before collecting.
response = requests.get(
'https://realtycrawl.dev/v1/meta/capabilities',
params={'platform': 'idealista'}
)
response.raise_for_status()
capabilities = response.json()// Check current source availability before collecting.
const response = await fetch(
'https://realtycrawl.dev/v1/meta/capabilities?platform=idealista'
);
if (!response.ok) throw new Error('Request failed');
const capabilities = await response.json();curl 'https://realtycrawl.dev/v1/meta/capabilities?platform=idealista'Capability excerpt · illustrative
{
"platform": "zillow",
"operation": "searchPlatformListings",
"status": "active",
"geographies": [
"US"
],
"execution": "sync"
}{
"platform": "redfin",
"operation": "searchPlatformListings",
"status": "active",
"geographies": [
"US"
],
"execution": "sync"
}{
"platform": "realtor",
"operation": "searchPlatformListings",
"status": "active",
"geographies": [
"US"
],
"execution": "sync"
}{
"platform": "rightmove",
"operation": "searchPlatformListings",
"status": "active",
"geographies": [
"GB"
],
"execution": "sync"
}{
"platform": "idealista",
"operation": "searchPlatformListings",
"status": "active",
"geographies": [
"ES"
],
"execution": "sync"
}Explore the sources behind the catalog
From a public source to a useful application
Choose what to collect, inspect the contract, and decide how it fits your product. RealtyCrawl supplies the request interface and the context needed to handle its response.
Common fields. Source-linked observations.
Keep currencies, area units, source identifiers, and observation times alongside request outcomes and credit usage.
Inspect response handlingDiscover before calling
Hand your assistant the API reference or connect the MCP server. Discover operations and their costs before allowing a tool to make a request.
Set up an agentStart with the work you need to do
Research a property, inspect listings, or compare a market — using selected sources and a collection plan you control.
Keep a record of the listing
Collect public listings from supported sources. Your application chooses the location, transaction type, collection schedule, and records to retain.
zillowSample: a listing observation in AustinUSD
redfinExample property asking pricesqft
realtorSource-linked property detailsUS
Keep the context behind the numbers
Compare source-labelled observations using their original currency, area unit, and transaction type. Retain source links so another person can check the evidence.
Sale72%
Rent21%
Other7%
Compare a market across collection windows
Save repeated samples of property searches. Measure changes in your own pipeline, with consistent locations and a clear account of incomplete source coverage.
Example market · illustrative historySample trend
Build a reference shelf for your market
Gather listing and property observations for your team. Attach collection dates, source URLs, and original units before using the data in a report or application.
Sample listingExample: listing first observed
Sample listingExample: asking price updated
Sample listingExample: no recent observation
Explore requests across 200 sources
43 documented operations to inspect. Choose a source, review the accepted inputs, and try a small request.
Choose a source to inspect and test
Zillow API2 endpoints documented
View docs curl -X POST 'https://realtycrawl.dev/v1/zillow/listings/search' \
-H "x-api-key: $REALTYCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{"location":{"kind":"bbox","bbox":[-97.82,30.2,-97.65,30.35]},"transaction":"sale"}'API key required
// Live requests require a RealtyCrawl API key.
// Copy the request to your backend and set REALTYCRAWL_API_KEY.
// Check source and operation availability before running a request.Make property data available to your assistant
Let your agent inspect the API before it calls it. The reference describes inputs, response metadata, and endpoint credit costs.
OpenAPIA contract your tools can inspect
Give the assistant a reference it can read
Point your coding assistant at OpenAPI to select a method and construct valid inputs. Authentication stays with the application that executes the request.
- Methods
- Parameters
- Examples
- Response schemas
- Authentication
- Credit costs
curl -s https://realtycrawl.dev/v1/openapi.jsonGuideText reference for tools and people
Read the setup notes
Keep the essential setup instructions close at hand: credentials, request limits, credits, and failure handling.
curl -s https://realtycrawl.dev/llms.txtOnboardingFor assisted development
You choose what the agent can spend
Create a key in your dashboard and store it with your application's secrets. Share the onboarding instructions with the agent that will build the integration.
curl -s https://realtycrawl.dev/agent-onboarding/SKILL.mdKnow the scope before you start
200Researched source platformsListings, property, rental, and market data
43Documented endpointsDocumented methods and inputs
1API key neededShared request metadata
100Credits for your initial evaluationTry a small, concrete use case.
Pay for useful data. Never for failures.
Start with 100 free credits. Buy a one-time pack when you need more. Failed provider calls are refunded automatically.
Free
Evaluate requests using trial credits.
100 credits$0
Start free- One-time signup credits
- Credits never expire
- REST & MCP
- Failed provider calls refunded
- Operation costs shown upfront
Starter
A starting balance for a small workload.
2,500 credits$15/ pack
Choose Starter- One-time payment · no renewal
- Credits never expire
- REST & MCP
- Failed provider calls refunded
- Operation costs shown upfront
Growth
More room for recurring collection jobs.
20,000 credits$49/ pack
Choose Growth- One-time payment · no renewal
- Credits never expire
- REST & MCP
- Failed provider calls refunded
- Operation costs shown upfront
Pro
A larger balance for sustained collection.
150,000 credits$299/ pack
Choose Pro- One-time payment · no renewal
- Credits never expire
- REST & MCP
- Failed provider calls refunded
- Operation costs shown upfront
Enterprise
Discuss your volume and purchasing requirements.
Custom volumeCustom
Talk to us- Volume and terms by agreement
- Credits never expire
- REST & MCP
- Failed provider calls refunded
- Operation costs shown upfront
Questions about pricing
Have a request we haven’t covered? Send us your use case
What is included in an initial evaluation?
Signup adds 100 trial credits without a payment card. Spend them on supported requests to inspect the returned data.
Where can I check the expected charge?
The operation page lists its credit amount, and each response reports actual usage. Failed provider calls do not leave a credit charge.
Does a catalog listing mean I can run it?
The 43 documented operations across 200 sources include preview coverage. Verify the specific call you need; unavailable operations fail without consuming credits.
How do additional credits work?
When checkout is enabled, the dashboard offers one-time USD packs: Starter at $15, Growth at $49, and Pro at $299. Purchases do not enable automatic recharging.
Do credits expire?
The balance remains until it is spent on API requests. Credit packs carry no monthly subscription or automatic renewal.
08 — Your first integration
Turn a public source into a product feature
200 sources in the catalog. Choose an operation, check the example, and test what your application needs.
curl "https://realtycrawl.dev/v1/meta/capabilities?platform=zillow"Notes for your next integration
View all posts
TutorialsReal Estate API with Python: Search and Read Listing Data
Build a small server-side Python client that checks capabilities, searches one source, preserves provenance, and controls request costs.
Read article
WorkflowsBuild a Real Estate Listing Price Monitor
Design a bounded collection workflow that detects observed asking-price changes, preserves history, and avoids false delisting alerts.
Read article
API designHow to Choose a Real Estate Data API for Your Application
Evaluate real estate APIs by workflow, source availability, identity, freshness, response quality, and the cost of a complete integration.
Read articleFrequently asked questions
Need help choosing a starting point? Describe your integration
Where should I begin evaluating RealtyCrawl?
Pick a real task: a property search, listing lookup, or source coverage check. Check the endpoint contract, make a small call, and confirm that the fields and availability fit your application before scaling up.
What is included in the platform catalog?
The catalog researches real estate portals and describes common property API operations. It also contains preview operations. A listing describes the intended contract; it does not guarantee that live access is enabled.
How much of the workflow does my app own?
RealtyCrawl handles the supported API request. You choose collection schedules, persistence, analysis, alerts, and how the returned information appears in your product.
When is my balance charged?
Successful calls use the credits listed for their endpoint. Inspect the response credit fields for the actual charge. Failed sources are refunded; inspect the operation contract for its charging rules.
How should I handle a busy service?
Treat a 429 response as a signal to slow down. Honor retry guidance when provided and bound your retries so a temporary limit does not create an endless job.
Which fields will a request return?
The outer response contract is shared, but the data object belongs to the selected operation. Inspect the reference and a sample response before assuming that a field exists.
Can I tell when a result was collected?
Record your request time and inspect cache information together with any source timestamps. Those timestamps describe different events; a cached response is not a new observation of the source.
Can an assistant discover the API?
Yes. Use the hosted or local MCP server, the installable skill, or the OpenAPI file. Store credentials in the tool's secret configuration and give the assistant a defined request budget.