What is the best real estate API?

What a real-estate data API does, and who calls it

The best real estate API for a workflow is the one whose geography, record type and observation date fit the question. An agent searching rental listings needs a different response from an analyst reviewing a tax assessment, a permit or a national housing series. Price becomes useful after that scope is established.

This page groups property records, listings and related research inputs by documented endpoint. It includes 9 services as of October 26, 2026. The table names the selected route behind each quote and leaves out 1 candidate that meet the listing checks but lack a matching priced task endpoint. A broad property description is not enough to infer an undocumented valuation, owner-contact or comparable-sales feed.

An address-based question often crosses several sources. A parcel record identifies the land, a listing describes an offer, an assessment roll records administrative values and an area index describes a larger market. Keep those objects separate in a combined report. Source links, periods, units and explicit missing reasons make it possible to inspect a result later, especially when an automated agent turns a collection of records into a narrative about an investment or a building.

What the 9 real-estate data services actually return

The classification follows documented endpoint products. It counts services per type, so a service offering more than one product can appear in more than one row. Each quote comes from the cheapest priced endpoint of that type, with its source route attached.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

Use this table to narrow the product before comparing hosts. A matching type identifies an advertised output, not verified accuracy or complete coverage of your input. The request schema, source period and returned missing-value states still need to fit the job. Read the service-specific notes below for limits that a broad product label cannot express.

The matched endpoint descriptions name HCAD for HCAD Harris County Property-Tax API, FRED for Stratalize and FEMA for Locus Report. Check the source-specific period and geography rather than treating an aggregate indicator as a parcel fact.

The 9 real-estate data APIs and their matching endpoint prices

One row per service, ordered by measured buyers. The price names the selected task route rather than an unrelated utility on the same host. Primary types determine the preferred quote; a service without a primary type uses its cheapest matching task endpoint.

$/CALL is the price of the endpoint named under it: the cheapest parcel records and property briefs and rental and sale listings endpoint of the service or, for a service without one, its cheapest property-data endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. PROPERTY-DATA ENDPOINTS counts the property-data endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its property-data endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

The buyer figure covers the host's measured payments, so it does not establish demand for this particular endpoint. A gateway can sell unrelated tools and a reseller can share an upstream source with another listing. Use these signals to investigate operational fit rather than inferring independent data collection or product quality from wallet counts.

How to choose a real-estate data API

Geography before price

Match country, county, municipality and property type before testing a query. A detailed county dataset can be useful inside its boundary while providing no evidence for a neighboring county. A successful example address does not establish that a search covers the next market on your list.

Identify the spatial unit

Parcel, address, postcode, ZIP, census area and service area are different units. Retain the original unit when attaching contextual data to a property. A utility service-area occurrence should not become a claim about a particular tap, and regional employment should not become observed foot traffic at a storefront.

Inspect the observation date

A listing retrieval, a tax year and a permit issue date describe different time relationships. Keep them in separate fields. When combining a recent listing with an older area indicator, make the periods visible in the output instead of labeling the packet current as a whole.

Expose underwriting assumptions

Store advertised and calculated yields separately. A calculation needs the income, expense, financing and occupancy assumptions that produced it. A construction cost proxy needs its units and size assumptions. Use the original record to support the calculation and inspect missing inputs before trusting a score or offer-range suggestion.

Which endpoint fits which job

Start with the job, then compare the candidates whose classified endpoints match it. The price in a job table is tied to those types, which can differ from the service's selected price in the main table. Do not assume that one host's entry quote covers another product it sells.

Resolve a property or parcel

Use a parcel account or exact address and check jurisdiction before joining the result. Preserve the source identifier, tax year and any match confidence. A parcel boundary, postal address and listing address can refer to different spatial objects; keep those distinctions when combining records.

Candidates today, most buyers first: Locus Report ($0.01/call, 23 buyers) · DwellData — Multifamily Real Estate Deals Feed ($0.02/call, 13 buyers) · Frontera Signal ($0.04/call, 8 buyers) · StableEstate ($0.01/call) · HCAD Harris County Property-Tax API ($0.02/call)

Find rental and sale opportunities

Define the geography, property type and freshness requirement before comparing asking prices. Keep original listing links and retrieval time. Separate asking price, advertised yield and computed underwriting; the last of these depends on assumptions that must stay visible to a reviewer.

Candidates today, most buyers first: DwellData — Multifamily Real Estate Deals Feed ($0.01/call, 13 buyers) · StableEstate ($0.01/call)

Research permits and construction context

Check which authority issued a permit and what its status means. A filed project cost, a retail material basket and an estimated rebuild proxy answer different budgeting questions. Record the observation period and units instead of treating them as interchangeable quotes for the same job.

Candidates today, most buyers first: Locus Report ($0.01/call, 23 buyers) · Frontera Signal ($0.01/call, 8 buyers)

Add neighborhood and environmental context

Keep parcel-level facts separate from ZIP, county, service-area and national aggregates. Require the source geography and observation period. A nearby reading can inform research without proving the condition at a particular building, and an aggregate housing index does not determine the value of one home.

Candidates today, most buyers first: RealEstatePulse ($0.03/call, 39 buyers) · Locus Report ($0.01/call, 23 buyers) · PayAPI Market UK Property Data API ($0.001/call, 22 buyers) · AgentFund US Economic, SEC & On-Chain Data ($0.005/call, generalist, 10 buyers) · Frontera Signal ($0.02/call, 8 buyers) · Stratalize ($0.02/call, 4 buyers) · StableEstate ($0.01/call)

Review distress signals and seller leads

Read the official source and current case status before interpreting a distress flag. A recorded delinquency or scheduled sale can change after collection. Preserve evidence dates and distinguish a public-record signal from a provider score or a generated research narrative.

Candidates today, most buyers first: Locus Report ($0.29/call, 23 buyers) · DwellData — Multifamily Real Estate Deals Feed ($0.03/call, 13 buyers) · Frontera Signal ($0.25/call, 8 buyers)

Service details and limits to check

The notes below are read from the provider's description and endpoint list captured on October 21, 2026. They attribute advertised capabilities and source information; x402-list has not independently tested the accuracy of the delivered data or generated output. Price, uptime and buyer tokens come from the current page model.

Locus Report

Locus Report describes parcel lookup and property-specific review packets from $0.01. Its parcel endpoint description explicitly excludes owner names and mailing addresses. The assessment tools start at $0.1 and describe comparison context rather than a market valuation or an appeal recommendation. Permit closeout and zoning start at $0.01, with covered municipal sources named in the endpoint description. Environmental products start at $0.01 and need their own spatial interpretation: a flood map, annual air-quality history and a service-area PFAS occurrence are different observations. The provider describes its rebuild-cost product as a proxy under stated size assumptions, rather than a contractor quote. Keep the source and geographic match for the exact property beside the output.

19 property-data endpoints of 21 · $0.01/call (POST /api/locus-parcel-lookup) · Base/SOL · uptime 30d 100% · 456 ms · 23 buyers in 30 days

Frontera Signal

Frontera Signal describes a Rio Grande Valley construction and property dataset. Its parcel route costs $0.04 and its description names Hidalgo County coverage with non-personal owner categories. Permit and project products start at $0.03, while market snapshots start at $0.02. Construction cost and material products start at $0.01. The endpoint descriptions distinguish filed project cost estimates, observed retail material prices and sparse labor ranges; those should remain separate columns. A filed estimate per square foot is not a completed project's actual cost. For the nearby-projects query, inspect coordinate coverage before interpreting a quiet radius as evidence that construction activity is absent.

12 property-data endpoints of 14 · $0.04/call (GET /api/v1/parcel) · Base · uptime 30d 100% · 220 ms · 8 buyers in 30 days

HCAD Harris County Property-Tax API

HCAD Harris County Property-Tax API lists /parcel/0010090000001/history at $0.02. The endpoint description says it returns annual assessed, appraised and market values from the HCAD roll as raw values without interpretation. The provider directs callers to obtain the parcel account from an address search. The service description also discusses protest outcomes, but the captured paid endpoint list documents the history route, so that is the product priced here. Keep the tax year, account and value field when comparing a sequence. An administrative market-value field on a tax roll does not by itself establish a current sale price, buyer offer or independent appraisal.

1 property-data endpoint of 1 · $0.02/call (GET /parcel/0010090000001/history) · Base · uptime 30d 100% · 978 ms · 0 buyers in 30 days

DwellData — Multifamily Real Estate Deals Feed

DwellData describes separate card-level listings and scored underwriting products. Listing-type calls start at $0.01; its basic route describes address, asking price, units, advertised cap rate, source link and freshness without the computed underwriting of the fuller feed. The per-address lookup costs $0.02. Distress calls start at $0.03 and describe Ohio tax-delinquency and sheriff-sale evidence with official source links. Seller leads start at $0.25. The provider says empty matching queries are free and absent fields carry typed reasons. Preserve those reasons and distinguish an advertised cap rate from a calculation based on the provider's stated income and debt assumptions.

8 property-data endpoints of 8 · $0.01/call (GET /api/deals/basic) · Base · uptime 30d 99.9% · 299 ms · 13 buyers in 30 days

StableEstate

StableEstate lists rental search, sale search, property-record search, individual address records and ZIP-level market aggregates. Listings start at $0.01, property records at $0.01 and market aggregates at $0.01. The property-record route is shown here as GET /api/properties/{address}, with an address placeholder instead of a residential example. The search endpoints list their own request inputs; a sample route does not establish coverage for your entire target region. The broader service description mentions value and rent estimates, but the captured endpoint list does not establish a distinct estimate route. Verify geographic availability and returned field definitions before using a record in an automated underwriting calculation.

10 property-data endpoints of 10 · $0.01/call (GET /api/properties/{address}) · Base · uptime 30d 100% · 245 ms · 0 buyers in 30 days

PayAPI Market UK Property Data API

PayAPI Market UK Property Data API lists postcode crime and flood-risk routes from $0.001. The endpoint descriptions name Police.uk and the Environment Agency. These are location-context products: a crime statistic describes its reporting area and period, and flood context depends on the relevant map or risk dataset. The broader description mentions additional UK property products, but the captured endpoint list supports the two context routes priced here. Do not budget for a transaction-price, valuation or rental-yield feed on the strength of the description alone. First check the postcode, source geography and response period against the property being assessed.

2 property-data endpoints of 2 · $0.001/call (POST /crime-stats) · Base · uptime 30d 99.9% · 500 ms · 22 buyers in 30 days

What the calls cost at different volumes

The median selected endpoint costs $0.01 per call. At that same request shape, 100,000 calls would cost $1,000.00. This multiplication is a comparison aid, not a provider invoice or a promise that an arbitrary request will use the reference quote.

Each service at the price of its main property-data endpoint, the one named in the table above.

Budget for useful results as well as submissions. A retry, an additional research step or a separate product can add another charge; no-match and partial-failure handling depend on the particular endpoint. For a variable body, model or input size, inspect the returned payment requirement for that exact request. Keep the quoted route and paid unit in the job record rather than projecting from the cheapest unrelated tool on a gateway.

How an agent reaches the HTTP 402 payment step

An unpaid request lets the caller inspect a payment requirement. The example below pairs the documented route with a real HTTP 402 payload previously captured by x402-list's monitor. Its capture date belongs to that evidence; it is not a claim that a paid result was tested today. The documented route has a reference quote of $0.02; inspect the challenge for the exact request terms.

curl -i 'https://hcad-api.canvas-cart.workers.dev/parcel/0010090000001/history'

HTTP/1.1 402 Payment Required

{
  "x402Version": 2,
  "resource": {
    "url": "https://hcad-api.canvas-cart.workers.dev/parcel/0010090000001/history"
  },
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0xA40Dadc75B69bEe8325E8089258235213293F8F4",
      "amount": "20000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    }
  ]
}

402 of HCAD Harris County Property-Tax API for GET /parcel/0010090000001/history, as stored by the monitor (terms unchanged since 2026-09-21, last check 2026-10-26 17:50 UTC), with every accepted payment exactly as stored and without error, extensions, resource.mimeType and resource.description, which are not payment terms: the full body is also on the service page, under Payment evidence. Amounts are in the asset's smallest unit: USDC has 6 decimals, so 20000 is $0.02.

Inspect the request schema before adapting the example. A documented POST endpoint needs the corresponding JSON inputs; a GET endpoint needs valid query values. Keep the payment requirement tied to the intended resource, network, asset and request. The captured challenge shows what payment access looks like. It does not prove that a paid call will return accurate output, complete a background job or satisfy the application's success criteria.

What this comparison measures

The listing requires an online, payment-ready service, a usable description, an advertised price and at least 90% measured uptime over 30 days. Task selection then reads its endpoint list and keeps the matching routes. Those listing checks establish a discovery threshold, not a certification of output accuracy.

Uptime is based on monitoring checks; average latency measures those checks. Buyer counts are distinct paying wallets observed for the service in the measurement window, with the limits described on the service page. A successful unpaid HTTP 402 response confirms a payment challenge rather than successful delivery after settlement.

Treat the provider's output contract and our monitoring as complementary evidence. Test a representative input, inspect source dates and missing states, and define a successful result before putting a recurring workflow on the endpoint. For comparison details, open the linked service page and the site's measurement methodology. Recheck the exact payment requirement when the input or advertised product changes.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.