Quick Answer
Make two calls. Look up the address with GET /api/public/property/address and read latitude and longitude from the record, then pass them to GET /api/public/premium/comparables. It returns nearby properties with a recorded sale within 1 mile and 18 months by default, up to 25 per call (50 max), and skips package and non-arm’s-length sales. Comparables are on every Realie plan.
Get an API keySummary
Realie’s comparables endpoint searches recorded sales around a point, not around an address string, so an address-based comps workflow is an address lookup followed by a comparables search. Each comparable is a property with a qualifying recorded sale: its price and date, address, coordinates, beds, baths, and square footage. The same search runs over the REST API, the Realie CLI, and the MCP server, on county records covering all 50 states, 3,100+ counties, and 180M+ addresses.
Why does getting comps for an address take two calls?
The comparables endpoint searches around a point. Its only required parameters are latitude and longitude, so the address has to become coordinates first. Realie’s address lookup returns them on the property record, as the parcel centroid, and the comparables search takes them from there.
First, look up the address. The street line and state are required; county and city narrow the match.
curl -H "Authorization: Bearer YOUR_API_KEY" "https://app.realie.ai/api/public/property/address?address=504%20LAVACA%20ST&state=TX"Then pass the record’s latitude and longitude to the comparables search. Radius and timeFrame are shown at their defaults.
curl -H "Authorization: Bearer YOUR_API_KEY" "https://app.realie.ai/api/public/premium/comparables?latitude=LATITUDE&longitude=LONGITUDE&radius=1&timeFrame=18"Both calls use the same API key and plan. A record leaves out latitude and longitude only when the parcel has no valid geocode; for that property, supply coordinates from another source.
Which parameters control a comparables search?
Only latitude and longitude are required. The other parameters narrow the search, and the response’s metadata.searchParams echoes them as parsed, with maxResults after its cap: a maxResults above 50 becomes 50 rather than being rejected. A radius above 25 miles and a timeFrame above 120 months are also capped without an error, but metadata.searchParams still shows the value you sent.
| Parameter | Default | What it does |
|---|---|---|
| latitude, longitude | Required | The point to search around, such as the subject property |
| radius | 1 mile | Search radius in miles |
| timeFrame | 18 months | How many months back to look for sales |
| maxResults | 25 | How many comparables to return, up to 50 |
| sqftMin, sqftMax | Not set | Square footage range |
| bedsMin, bedsMax | Not set | Bedroom range |
| bathsMin, bathsMax | Not set | Bathroom range |
| priceMin, priceMax | Not set | Sale price range; flagged package sales stay excluded even when their price is in range |
| propertyType | Not set | any, condo, or house |
| full | false | true adds each comparable’s full property record |
Which sales count as comparables?
Every comparable is a recorded sale from county public records, with a sale price and date, inside your radius and look-back window. The endpoint does not return MLS listings, active or pending listings, listing photos, or rent comparables, and Realie does not produce rent estimates.
Two kinds of recorded sale are never used. A package sale, one deed that conveyed several parcels, records the total price for all of them, so it would overstate any one property. A sale marked not arm’s-length is skipped too, while a sale whose arm’s-length status is unknown still qualifies. One exception: comparables drawn from previous-generation data, for example on an account Realie support has kept on it, carry no package-sale flag and can include package sales.
Because each comparable is a recorded sale, every number traces back to a county record. For the full transaction trail on one property, see How do I get property sales history by API?
What does each comparable include?
Each comparable is a compact row: the address, latitude and longitude, totalBedrooms, totalBathrooms, a square-footage figure (realieSquareFootage), and the qualifying sale as transferPrice and transferDateObject. The response lists the rows under comparables, with metadata.count and metadata.searchParams beside them.
Add full=true (--full in the CLI) to attach each comparable’s full property record as a property object, in the same shape your account gets from a parcel ID lookup. The comparables, their order, and the cost of the call stay the same; only the response grows. Sale fields inside that record describe the parcel’s own latest sale, which can differ from the qualifying sale on the row.
Property records also carry a comparable-sales value estimate, compModelValue, where Realie can produce one. How it works next to the machine-learning estimate is covered in Where can I find automated property valuation estimates (AVM) by API?
How do I pull comparables from the CLI or an AI agent?
The Realie CLI mirrors the endpoint as realie comparables, with the same parameters as kebab-case flags. Add --json for the raw response, and --full for full records.
realie comparables --latitude 30.2672 --longitude -97.7431 --time-frame 12 --jsonOver MCP, the comparables tool takes the same parameters and returns at most 10 comparables per call, sized for a model’s context. An agent runs the same two steps as REST: address_lookup for the coordinates, then comparables.
For a ChatGPT workflow that keeps the sale evidence attached to each comp, see How do I find comparable property sales with ChatGPT in 2026?
Which Realie plans include comparables?
Every plan. The endpoint path still contains /premium/, a leftover from older naming, but comparables are available on Free and on every paid plan, with the same parameters and data. A successful search counts as one call whether it returns 5 comparables or 50, with or without full=true. A search that finds none returns 404 and is not billed.
Plans differ in the calls they include: Free includes 25 calls a month, $50/mo includes 1,250, $150/mo includes 6,000, $350/mo includes 30,000, and enterprise pricing at $600/mo includes 100,000. See plans and pricing.
Sources
Frequently asked questions
- Is there an API for comparable sales?
- Yes. Realie’s comparables endpoint, GET /api/public/premium/comparables, returns nearby properties with a recorded sale inside a radius and look-back window you set, each with its sale price and date. It is on every plan, and it is also available as realie comparables in the CLI and as the comparables tool on the MCP server.
- Can I search comparables by address instead of coordinates?
- Not in one call. The comparables endpoint requires latitude and longitude. Look the address up first with the address lookup endpoint, which returns the parcel’s latitude and longitude, then pass them to comparables. Each of the two calls counts as one call on your plan when it succeeds.
- Does the comparables API include MLS listings or rent comps?
- No. Comparables are recorded sales from county public records. Realie does not return MLS listings, active or pending listings, listing photos, or rent estimates, so use another source if you need asking prices or rental comparables.
- Why is a nearby sale missing from my comps?
- It may fall outside the radius or timeFrame, miss a beds, baths, size, price, or property type filter, or be a package sale or a sale marked not arm’s-length, which are never used. The search also stops at maxResults, 25 by default and 50 at most, so widen the filters or raise maxResults to see more.
- How many comparables does one call return?
- Up to 25 by default, and up to 50 with maxResults, over REST and the CLI. The MCP comparables tool returns at most 10 per call. A search that finds no comparables returns 404 and does not count against your plan.
- Are comparables a premium add-on?
- No. The path /api/public/premium/comparables keeps an older name, but comparables are on every Realie plan, Free included, and a successful search counts as one call like any other endpoint.