Get Sold Count by ZIP
get_sold_count_by_zipWhat it returns
Just the count of residential properties sold in a ZIP within the last 365 days. Same dedup + recency rules as sold-by-zip, but only the integer count — useful when you don't need the property details and want to minimize cost.
When to use it
Display market velocity in a header widget (no need to render rows).
Drive a chart of monthly sales trend across many ZIPs cheaply.
Pre-check whether a ZIP has enough comp activity before calling
sold-by-zip.
Date range
By default the endpoint returns the full trailing 365 days. Pass start_date, end_date, or both (YYYY-MM-DD) to narrow that to a specific window — for example one calendar month at a time instead of re-pulling the whole year on every poll:
?zip=95630&start_date=2026-08-01&end_date=2026-08-31Both bounds are optional and inclusive, and both are independent: pass only start_date for an open-ended window, or only end_date to cut off recent sales. Passing neither leaves existing behaviour unchanged.
Either bound must fall within the last 365 days. An older date returns 400 naming the earliest date we can serve, rather than quietly returning a partial set.
Property type
Pass property_type (one value or a comma-separated list, same values as sold-by-zip) to count only those types:
?zip=65802&property_type=single_familyOmitting it counts every type. Unknown values return 400.
Pricing
1 credit per call regardless of the count.
FAQ
What's the difference between this and sold-by-zip?
This returns one integer (1 credit). sold-by-zip returns the full list (1 credit per 20 properties). Use this for cost-efficient screening; use sold-by-zip when you need details.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"zip": "<zip>"
},
"name": "get_sold_count_by_zip"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes | 5-digit US ZIP code. | |
| end_date | No | Latest sale date to include, as `YYYY-MM-DD`. Optional — omit for no upper bound. Inclusive: a sale on this exact date is returned. Must be on or after `start_date` and within the last 365 days. | |
| start_date | No | Earliest sale date to include, as `YYYY-MM-DD`. Optional — omit for the full 365-day window. Inclusive: a sale on this exact date is returned. Must fall within the last 365 days; anything older returns `400`, since that is the whole window we retain. | |
| property_type | No | Count only these property types. One value or a comma-separated list, e.g. `single_family` or `single_family,townhomes`. Optional — omit for every type. Values are the ones the response's `property_type` field carries, chiefly `single_family`, `condos`, `townhomes`, `multi_family`, `apartment`, `mobile`, `duplex_triplex`, `coop`, `condo`, `land`, `farm`, `other`. Case-insensitive; `-` and spaces are read as `_`. An unknown value returns `400` listing the full accepted set. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||