Microburbs Australian Property Data MCP Server

by com-microburbs Your server? Claim it

answering

Microburbs Australian Property Data is answering right now. Last checked 15 min ago. It exposes 200 tools.

Australian property and suburb data: valuations, sales, rents, schools, risk and zoning.

Uptime history 55 days of history · worst day 89%

55 days agonow

100.0%

Uptime 24h

91 of 91 checks

200

Tools

read from the server

1032 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 212

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

6 Nov 128 tool descriptions were rewritten area_stats_fields, economics_cpi, economics_cpi_adjust and 125 more

6 Nov 8 tools changed the parameters they ask for area_stats_fields, economics_cpi, economics_cpi_adjust and 5 more

6 Nov 3 tools disappeared properties_valuation_all, properties_valuation_avm, properties_valuation_value_series

5 Nov 30 tools appeared economics_cash_rate, economics_cash_rate_series, economics_cpi and 27 more

5 Nov 17 tool descriptions were rewritten18 times that day mbs_profile, properties_surroundings_tenure, suburbs_demographics_tenure and 14 more

5 Nov a tool disappeared get_series_v1_economics_series

20 Oct a tool appeared suburbs_listings_for_rent

20 Oct a tool description was rewritten suburbs_listings_for_sale

20 Oct a tool changed the parameters it asks for suburbs_listings_for_sale

6 Oct 12 tool descriptions were rewritten me, properties_basics_all, properties_comparables_all and 9 more

and 10 more, back to 17 September 2026

Microburbs Australian Property Data missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add property-data --transport http https://api.microburbs.com.au/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.microburbs.com.au/mcp

~/.codex/config.toml

[mcp_servers.property-data]
url = "https://api.microburbs.com.au/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "property-data": {
      "url": "https://api.microburbs.com.au/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "property-data": {
      "type": "http",
      "url": "https://api.microburbs.com.au/mcp"
    }
  }
}

Available tools 200

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

suburbs

suburbs_crime_breakdown

Shown in the suburb report as the breakdown table inside the 'Crime' card in the Risks section. Per-crime-type rates (predicted incidents per 100,000 residents per year) for the suburb vs national medians.

suburbs_crime_by_mesh_block

Shown in the suburb report as the 'Crime' map layer in the Risks section. Total crime rate for every mesh block in the suburb, keyed by mesh-block code. Values are predicted incidents per 100,000 residents per year (see the payload's `unit` / `definition` keys).

suburbs_crime_summary

Shown in the suburb report as the 'Crime' card in the Risks section. Suburb and national total-crime medians (predicted incidents per 100,000 residents per year) with a vs-national verdict.

suburbs_demographics_age

Population by age bracket and gender.

suburbs_demographics_all

Who lives in the suburb: population by age bracket and gender, and households by income bracket. Two calls bundled, priced as the sum. Tenure, employment, family make-up, schooling and the rest of the Suburb - Demographics family are separate.

suburbs_demographics_ancestry_map

The dominant ancestry (and its share) in each of the suburb's mesh blocks, plus suburb-level ancestry shares. Pilot coverage.

suburbs_demographics_business

Shown in the suburb report as the 'Local business mix' section heading in the Demographics section. ABN industry-mix pattern (Diverse / Professional-services-heavy / Mining-exposed / Low-commercial residential) plus the POI categories unusually common in the suburb, with named examples.

suburbs_demographics_cohorts

How the suburb ranks inside its SA4 region and against its touching neighbours on renter share, welfare dependency, overseas-born parents and public housing.

suburbs_demographics_cultural_integration

Shown in the suburb report as the 'Cultural Integration' card in the Demographics section. Suburb cultural-integration composite (0-100) with national percentile and tier, plus the per-mesh-block scores behind it.

suburbs_demographics_income

Household income breakdown by bracket.

suburbs_demographics_income_map

Shown in the suburb report as the 'Income' map layer in the Demographics section. Median weekly household income for every mesh block in the suburb, plus the suburb median, national percentile and highest/lowest pockets.

suburbs_demographics_population_history

Shown in the suburb report as the 'Population' chart in the Demographics section. Total suburb population is `current_population` (2021), alongside suburb counts for 2011, 2016 and 2021 and the LGA's yearly population series with a 10-year modelled projection tail. Use this route for questions such as "what is the total population of Clarkson?

suburbs_demographics_population_map

Shown in the suburb report as the 'Population' map layer in the Demographics section. Residents and dwellings on every mesh block in the suburb, with the suburb totals. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_demographics_private_school

Shown in the suburb report as the 'Private School Students' card in the Demographics section. Share of residents attending Catholic / Independent schools — suburb rollup plus the per-mesh-block shares behind it.

suburbs_demographics_single_parents

Shown in the suburb report as the 'Single Parents' card in the Demographics section. Single-parent-family share for the suburb against the pinned national median, with the associated capital-growth impact.

suburbs_demographics_single_parents_map

Shown in the suburb report as the 'Single parents' map layer in the Demographics section. Single-parent families as a share of families for every mesh block in the suburb, percent 0-100. Near-empty blocks are left out. The suburb figure is ``/demographics/single-parents``. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_demographics_tenure

Shown in the suburb report as the 'Housing Tenure' card in the Demographics section. Explicit total owner-occupation rate plus owned-outright / mortgaged / renting / public-housing shares — a suburb rollup and the per-mesh-block modelled shares. `owner_occupied_pct` is the requested headline; it equals owned outright plus mortgaged and is null if either is absent. `census_year` gives the reference year of the figures (2021).

suburbs_demographics_underclass_drag

Shown in the suburb report as the 'Underclass Drag' card in the Demographics section. Welfare-dependency and public-housing shares with the suburb's underclass tier (High / Mid / Low) and the capital-growth impact associated with that tier. Regional and neighbour ranks for the same two metrics are served by `/demographics/cohorts`.

suburbs_demographics_unemployment

Shown in the suburb report as the 'Unemployment' card in the Demographics section. Labour-force-weighted unemployment rate for the suburb against the pinned national median, plus the per-mesh-block shares behind it.

suburbs_demographics_voting

Shown in the suburb report as the 'Voting' card in the Demographics section. Projected first-preference shares per party, aggregated across the suburb's mesh blocks (booth-derived model — not an actual vote).

suburbs_demographics_voting_map

Shown in the suburb report as the 'Voting (winning party)' map layer in the Demographics section. Projected winning party, runner-up and margin for every mesh block in the suburb at a federal election held May 2026 — a projection, not an actual vote. The suburb-wide profile is ``/demographics/voting``. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_development_all

Shown in the suburb report as the 'Development Applications' card in the Development section. What is being built in the suburb: the count of development applications on record, and the list itself with each application's address, type and status. Read it as supply coming down the pipeline, and as a signal of where a suburb is changing.

suburbs_development_applications

Shown in the suburb report as the 'Development Applications' card in the Development section. Development applications in the suburb, newest first, with category counts. Paginated with `limit`/`offset`: `total_available` is every application we hold for the suburb, `total` is how many this page returned, and `next_offset` is the next page's offset (null on the last). `min_date` / `max_date` span the full history. Each page is one call at a flat price.

suburbs_development_building_controls

Height-of-building and floor-space-ratio control polygons with band summaries.

suburbs_development_construction_activity

Satellite-detected construction change per mesh block plus a suburb rollup.

suburbs_development_council_intelligence

Shown in the suburb report as the 'Council Intelligence' table in the Development section. Council capex / project-pipeline signals extracted from the LGA's meeting minutes — each with stage, dollar value, location and time horizon — plus a rollup of the total pipeline in dollars.

suburbs_development_council_rates

Shown in the suburb report as the 'Council Rates' card in the Development section. Average annual residential council rate for the suburb's LGA.

suburbs_development_da_count

Shown in the suburb report as the 'Applications' headline figure in the Development section. Count of recent development applications in the suburb.

suburbs_development_da_list

Shown in the suburb report as the 'Development Applications' table in the Development section. Recent development applications lodged in the suburb.

suburbs_development_density

Shown in the suburb report as the 'Density' card in the Development section. Dwellings and people per km², plus the land area and counts behind them.

suburbs_development_density_map

Shown in the suburb report as the 'Density' map layer in the Development section. Dwellings per km² for every mesh block in the suburb, with the dwelling count and area it is computed from and a Low → Very high band. The suburb-wide figure is ``/development/density``. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_development_new_dwellings_map

Shown in the suburb report as the 'Construction' card and map layer in the Development section. How many development applications for new dwellings were lodged in each mesh block of the suburb, from the newest 2,000 applications. Every block is listed, 0 where none were. The individual applications are at ``/development/applications``. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_development_profile

Shown in the suburb report as the 'Density' card body in the Development section. Dwelling-mix scalars — apartment share and average lot size.

suburbs_development_supply

Shown in the suburb report as the 'Supply 2km' map layer (explorer) in the Development section. New dwellings (last 24 months) split units vs houses per mesh block plus a rollup.

suburbs_development_zoning_map

Shown in the suburb report as the 'Zoning' card in the Development section. Zoning polygons clipped to the suburb, with per-class and parent-group area shares.

suburbs_ethnicity_all

Cultural make-up of the suburb: ancestry breakdown and country of birth, each as a share of residents. Useful for understanding who a suburb's buyers and renters are. The map version, which splits these by mesh block, is a separate call.

suburbs_ethnicity_ancestry

Ancestry breakdown.

suburbs_ethnicity_birthplace

Country-of-birth breakdown.

suburbs_finder_count

How many suburbs match the filter, without paying per row. 5c. Use this to size a result before searching: /search is capped at 25 rows per call, so `total` here tells you how many `offset` pages you need. **Price: 5¢ per call.**

suburbs_finder_fields

Every field you can filter / sort on, with its label and unit. 0c. Houses and units are separate keys: the `unit`-prefixed ones (`unitMedianPrice`, `unitGrossYield`, `unitMedianRent`, …) are the apartment market, the unprefixed market keys are houses, and both can be filtered in the same query. Unit fields are NOT nationally populated — they only exist where a suburb has a unit market (roughly 13-54% of suburbs depending on the field), so a suburb with no unit market simply won't match a unit filter. **Free.**

suburbs_finder_regions

SA4 regions grouped by state — the values accepted by `states` / `regions` on search. 0c. **Free.**

suburbs_finder_search

Boolean-AND range filter over suburb metrics, single-column sort, paginated. Every row carries its `rank` — position in the ranked result (1 = top of the sort, out of `meta.total`). When sorting by a median or a growth, the actual value is also shown for the first 5 and last 5 rows of the page; for any other suburb's number, call the per-field endpoint (market/*, forecast/*). **Paging:** a page is capped at 25 rows. A bigger `limit` is clamped, not rejected — so always read `meta`: `total` is the full match count, `has_more` says whether rows remain, and `next_offset` is the `offset` to pass for the next page. A "top 50" needs two calls, each charged. Flat 30c. **Price: 30¢ per call.**

suburbs_forecast_sale

1-year sale-price growth forecast (low / most-likely / high).

suburbs_hero_neighbours

Nearest neighbouring suburbs with distance in km, closest first.

suburbs_hero_price_growth_12mo

12-month sale-price growth by property type (house / unit).

suburbs_hero_summary

State, SA3/SA4, postcode, population, dwellings and centroid for the suburb.

suburbs_lifestyle_cbd

Shown in the suburb report as the 'Distance to {City} CBD' table row in the Lifestyle section. Straight-line distance to the nearest city and to the nearest capital, in km. Both, because they answer different questions and are often nowhere near each other: Belmont North is 14 km from Newcastle and 108 km from Sydney. `nearest_city` is usually what a buyer means by "how far is town". The top-level `city` / `distance_km` fields are DEPRECATED. They still describe the CAPITAL, unchanged, so existing callers are unaffected — read `capital_city` or `nearest_city` instead.

suburbs_lifestyle_landmarks

Nearest beach and hospital with straight-line distances (null = none within ~50 km).

suburbs_lifestyle_livability

Shown in the suburb report as the 'Livability' card in the Lifestyle section. Livability scores (0–100) per dimension, aggregated from mesh-block scores, with the SA4 benchmark.

suburbs_lifestyle_livability_map

All seven livability dimensions — affluence, lifestyle, hip, convenience, family, safety, tranquility — scored 0-100 for every mesh block in the suburb, each with its human band. Averaging a dimension across the mesh blocks reproduces the suburb figure at ``/lifestyle/livability``. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_lifestyle_narrative

Shown in the suburb report as the 'Livability' card sentences in the Lifestyle section. One plain-English sentence per livability dimension for the suburb.

suburbs_lifestyle_poi_impacts

What the absence of petrol stations, fast food and bottle shops near sold properties was worth.

suburbs_lifestyle_pois

Shown in the suburb report as the 'Amenities' card and map layer in the Lifestyle section. Every named venue / amenity in the suburb as GeoJSON Point features, plus a per-category count. Each point carries `name`, a broad `category` (Restaurant / Cafe, Shopping, Health, Entertainment, Sport & Fitness, Education, …) and a finer `subtype` (e.g. `pub`, `bar`, `cafe`, `restaurant`, `gym`, `supermarket`, `school`, `pharmacy`). This is the endpoint for "what / how many <venue type> are in this suburb" and "name the pubs / cafes / gyms in X" — filter or count the features on `subtype`, and read real venue names from `name`. The top-level `categories` array gives the broad-category counts without walking the list. Unpaged by default. Big suburbs are big — Sydney is ~3.7 MB of features — so pass `limit`/`offset` (or narrow with `category`) when you don't need them all. `count` and `categories` always describe the whole suburb, so paging never hides the totals. Flat price per call regardless of page size.

suburbs_lifestyle_summary

POI category breakdown, terrain scalars, nearest train/shop and beach/hospital flags.

suburbs_list

List Australian suburbs (SALs). Always returns `{suburb, state}` per row so SAL-name collisions across states are unambiguous. With no filter you get 1000 suburbs at a time, alphabetically — page with `offset` (1000, 2000, …) for the rest. Pass any of the filters to narrow: state / lga / sa4 / sa3 / postcode / q (name search). Filters combine (AND). Flat cost regardless of how many rows come back. **Name search (`q`) is typo-tolerant.** It tries an exact match, then substring, then a fuzzy near-miss, and returns `match` (`exact` / `contains` / `fuzzy`) and `score` on every row so you can see which happened. **Always tell the user which suburb you resolved to, and its state, before quoting numbers for it.** A fuzzy match is a suggestion, not a confirmation — `rokeby` is one letter from Kokeby in Western Australia and Rokeby exists in both Tasmania and Victoria. If more than one candidate is plausible, ask rather than pick. When `q` is combined with `state`, the state is a **preference, not a filter**: in-state candidates rank first, but a suburb of that name in another state is still returned rather than hidden, so a near-miss becomes "Seaview is in Victoria, not Tasmania" instead of "no data". Every other filter stays a strict AND. **Free.**

suburbs_listings_for_rent

Rental listings live right now in the suburb, with address, weekly rent and the advertised rent line, beds/baths/cars, coordinates, an `off_market` flag and the leasing agency. Same paging, filters and withholding rule as for-sale.

suburbs_listings_for_sale

Shown in the suburb report as the 'For sale' table tab in the Properties section. Current for-sale listings in the suburb, with address, price and the advertised price line (with its low/high range when one is stated), beds/baths/cars, land and floor area, coordinates, an `off_market` flag, and the selling agency with its own listing page and named agents. A listing seen on only one major portal, with no agency page of its own, keeps its address, type and agency name but not its advertised facts: the same rule our property finder applies. `total` is the full number on the market (computed before paging), so a count is accurate even when the rows are capped. Page through every listing with `limit`/`offset` — `next_offset` is the next page's offset, null on the last page; order is newest listing first and stable across pages. Each page is one call at a flat price. Set `verbose=true` for the agent's full description text; set `off_market=true` for off-market listings only.

suburbs_market_affordability

Shown in the suburb report as the 'Affordability' card in the Market section. Our affordability index for the suburb's postcode area.

suburbs_market_all

The eight headline market indicators in one call: median sale price and median rent (each with its full history), 5-year price growth, gross yield, days on market, and transaction volume. **This is a core set, not every market endpoint.** The `Suburb - Market` family has 29 endpoints; this bundles 8 of them, priced sum-of-parts. The path is `/market/all` for historical reasons — it is not "all". Supply, vacancy, growth drivers, affordability, mortgage stress, investor concentration, land values, repeat sales, bedroom stats and the per-mesh-block maps are separate calls, so you only pay for what you ask for.

suburbs_market_bedroom_stats

Shown in the suburb report as the 'Figures by bedroom' table in the Market section. House/unit price, sales volume, median bath/car/land, and stock mix per bedroom count.

suburbs_market_built_year

Shown in the suburb report as the 'Built Year' card in the Market section. Estimated build-year profile — suburb aggregate + per-mesh-block medians.

suburbs_market_comparable_suburbs

Same-SA3 comparable-suburb candidates (canonical SAL names).

suburbs_market_days_on_market

Shown in the suburb report as the 'Days on Market (Houses)' card in the Overview section. Median days on market for current listings.

suburbs_market_days_on_market_benchmark

Shown in the suburb report as the 'Days on Market' city column of the comparison grid in the Market section. Median days on market across the suburb's greater region (GCCSA) — compare with /market/days-on-market.

suburbs_market_growth_drivers

Per-indicator capital-growth attribution for the suburb. Each row pairs the suburb's own value for an indicator with the capital-growth differential our matched studies attribute to it, in percentage points. Covers supply & demand pressure, market signals, environmental risks and demographic composition.

suburbs_market_growth_map

Past price growth over 1, 3, 5 and 10 years for every mesh block in the suburb, in percent — cumulative over each horizon. Houses, or units where the block has no house figure. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_market_investor_concentration

Shown in the suburb report as the 'Investor Concentration' card in the Market section. Rental (investor) share per mesh block, with a suburb-wide rollup.

suburbs_market_land_values

Shown in the suburb report as the 'Land Value' card in the Market section. Suburb land-value medians ($/sqm, lot size, land share of price) + per-mesh-block $/sqm.

suburbs_market_median_price_map

Shown in the suburb report as the 'Median sale price' card and map layer in the Market section. Median house price for every mesh block in the suburb, with its modal street name, plus the dearest and cheapest pockets. Values only — the matching polygons come from ``/shapes/mesh-blocks``.

suburbs_market_median_rent

Shown in the suburb report as the 'Median Rent/wk' headline figure in the Market section. Latest median weekly rent for the suburb.

suburbs_market_median_rent_series

Shown in the suburb report as the 'Median Rent' chart tab in the Market section. Full median weekly-rent observation history for the suburb, including 2024 and 2025 where the suburb has coverage. Older observations are generally month-end and recent observations can be weekly; this is not a uniformly quarterly series. Values are advertised median AUD per week.

suburbs_market_median_sale_price

Shown in the suburb report as the 'Median Sale Price' headline figure in the Market section. Latest median sale price for the suburb.

suburbs_market_median_sale_price_series

Shown in the suburb report as the 'Median Sale Price' chart tab in the Market section. Full median sale-price observation history for the suburb. Well-covered suburbs extend back 20+ years; coverage and observation frequency vary. This is the raw historical series needed to calculate a stated 20-year return, not a precomputed "consistent growth" score or a forecast.

suburbs_market_months_of_supply

Shown in the suburb report as the 'Months of Supply' card in the Overview section. How many months the current for-sale stock would take to clear at the suburb's current sales rate. Under 2 months is a seller's market.

suburbs_market_mortgage_stress

Shown in the suburb report as the 'Mortgage Stress' card in the Market section. Mortgage-stress score (0-100) for the suburb, with per-mesh-block breakdown.

suburbs_market_negative_gearing_map

Shown in the suburb report as the 'Negative gearing' map layer in the Market section. Share of each mesh block's investment properties that are negatively geared (our estimate, 0-100), with how many properties it is taken over. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_market_price_growth

Shown in the suburb report as the 'Historical Total Past Growth for Houses' chart in the Market section. Past compound sale-price growth over 1 / 3 / 5 / 10 years, by property type (decimal). The 3y / 10y figures are the same ones the Suburb Finder ranks on.

suburbs_market_price_growth_5y

5-year compound sale-price growth (decimal).

suburbs_market_recent_price_movement

Shown in the suburb report as the 'Recent Price Movement' table in the Market section. The last four weekly smart-median observations — house price, unit price and house rent — each with its week-on-week percentage change.

suburbs_market_rent_map

Shown in the suburb report as the 'Weekly Rent' map layer in the Market section. Median advertised weekly house rent for every mesh block in the suburb, with its modal street name, plus the dearest and cheapest pockets. Values only — the matching polygons come from ``/shapes/mesh-blocks``.

suburbs_market_repeat_sales

Shown in the suburb report as the 'Recent Repeat Sales' card in the Market section. Realised resale growth — summary + individual buy/sell pairs (max 500).

suburbs_market_stock_on_market

Shown in the suburb report as the 'Stock on Market' card in the Overview section. Properties currently listed for sale in the suburb, split house/unit, with the suburb's rank among its peers.

suburbs_market_strata_levies

Median estimated annual strata levy for the suburb.

suburbs_market_supply_pressure

Shown in the suburb report as the 'Supply Pressure' map layer (full-screen map explorer) in the Market section. For-sale listings per 100 dwellings (90 days) — per mesh block + suburb rollup.

suburbs_market_transaction_volume

Shown in the suburb report as the 'Sales Volume' chart tab in the Market section. Recent sale-transaction count for the suburb.

suburbs_market_vacancy_map

Shown in the suburb report as the 'Vacancy rate' map layer in the Market section. Calibrated rental-vacancy rate for each mesh block in the suburb.

suburbs_market_vacancy_rate

Shown in the suburb report as the 'Vacancy Rate' card in the Overview section. Suburb-wide rental vacancy rate by property type, as a decimal fraction (0.00842 = 0.84%). Use `/market/vacancy-map` for the per-mesh-block surface.

suburbs_market_vacancy_rate_series

Shown in the suburb report as the 'Vacancy Rate' chart tab in the Market section. Full rental-vacancy history by property type, decimal fractions.

suburbs_market_yield_map

Shown in the suburb report as the 'Gross Yield' map layer in the Market section. Gross rental yield for every mesh block in the suburb — weekly rent x 52 over median price — with both inputs returned so the number is checkable, plus the best- and worst-yielding pockets. Values only; polygons come from ``/shapes/mesh-blocks``.

suburbs_market_yield_pct

Shown in the suburb report as the 'Gross Yield' headline figure in the Market section. Gross rental yield = median rent annualised / median sale price.

suburbs_market_yield_pct_series

Shown in the suburb report as the 'Gross Yield' chart tab in the Market section. Full gross-rental-yield history by property type, decimal fractions.

suburbs_mesh_blocks_building

**What are the homes like?** For every mesh block in the suburb: how many properties, the share of houses and strata, median bedrooms, bathrooms and building size, building height, and recent construction. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_business

**What's nearby?** For every mesh block in the suburb: distance to the nearest supermarket, cafe, restaurant, bakery, pharmacy, GP and pub, and how many cafes, restaurants and supermarkets are within 320 m. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_condition

**What condition are the homes in?** For every mesh block in the suburb, how its listings describe the homes: renovated, updated kitchens and bathrooms, renovation potential, original features, air conditioning, and how many listings the shares are read from. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_crime

**Beta.** The figures behind this topic have not been validated against an independent source, so it is not sold at the same confidence as the other mesh-block topics. Every response says `beta: true` and carries a `beta_notice`. **Is this place safe?** Estimated crime rates for every mesh block in the suburb — all crime and eight types, per 100,000 residents a year — with where each block sits among the blocks in its suburb and nationally. From our mesh-block crime model, calibrated in November 2026 so each area's blocks add up to what police recorded there. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_environment

**Is it green and quiet?** For every mesh block in the suburb: greenness and vegetation cover from satellite and how it has changed, a noise score, and solar panels on listings and small-scale installations. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_forecast

**Beta.** The figures behind this topic have not been validated against an independent source, so it is not sold at the same confidence as the other mesh-block topics. Every response says `beta: true` and carries a `beta_notice`. **What's the outlook?** Modelled forecasts for every mesh block in the suburb: owner-occupation in 2026, capital growth, the chance of a rezoning within five years, and future building height. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_hazard

**Is it exposed to flood, fire or erosion?** For every mesh block in the suburb: whether the block sits inside flood planning, flood overlay, bushfire-prone or erosion-prone areas, risk scores for flood, fire, coast and ground movement, and the slope of its homes. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_income

**How much do people here earn?** For every mesh block in the suburb: median household, personal and family income for the surrounding area, and salary, deductions and tax for the postcode. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_parcels

**Beta.** The figures behind this topic have not been validated against an independent source, so it is not sold at the same confidence as the other mesh-block topics. Every response says `beta: true` and carries a `beta_notice`. **How big are the blocks of land?** For every mesh block in the suburb: median and spread of lot sizes, lot shape, floor space ratio, the minimum lot size under the planning rules, and the number of land parcels. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_rent

**What does it cost to rent here?** For every mesh block in the suburb: advertised weekly rents recorded on the block (median, range, how many properties, typical year), our weekly rent and gross yield for the block, and the median rent for the surrounding area. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_signals

**Beta.** The figures behind this topic have not been validated against an independent source, so it is not sold at the same confidence as the other mesh-block topics. Every response says `beta: true` and carries a `beta_notice`. **Is this block moving?** For every mesh block in the suburb: recent price growth on the block against its suburb, long-run house value growth, and the share of properties recently listed for rent. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_stress

**Is anyone here under financial pressure?** For every mesh block in the suburb: unemployment in the surrounding area, JobSeeker recipients in the postcode, and estimated mortgage arrears, forced sales and personal insolvencies. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_tenure

**Who owns and who rents here?** For every mesh block in the suburb: shares of homes owned outright, mortgaged and rented in the surrounding area, the median mortgage repayment, the share of properties ever listed for rent, and rent assistance recipients in the postcode. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_mesh_blocks_transport

**How do you get around from here?** For every mesh block in the suburb: distance to the nearest bus stop, train station and tram stop, bus stops within 320 m, and how many workers commute by public transport. One entry per mesh block in the suburb under `mesh_blocks`, each with its `mb_code`, `population` and `dwellings`. Values only — the matching polygons come from `/shapes/mesh-blocks`. Every field carries `provenance` — `measured` (at this block), `measured_wider_area` (measured for the SA1 or postcode and repeated on every block in it), `estimate` (our model) or `not_recorded` (not labelled yet) — plus `how`, one sentence on how the number was arrived at (empty when `not_recorded`).

suburbs_profile

The suburb's upward geography chain — LGA, SA2/3/4, GCCSA, state, postcode. Use ``/v1/suburbs/list`` to discover canonical SAL names (and filter by state / LGA / SA4 / postcode).

suburbs_risks_all

Natural-hazard exposure for the suburb: how much of its area sits inside a designated bushfire-prone area and inside a modelled flood overlay, each with a plain risk band and the number of distinct hazard polygons. Pass `geojson=true` to get the hazard shapes themselves, clipped to the suburb boundary, in the same call. Slope, heritage, power lines and the per-property hazard counts are separate calls.

suburbs_risks_bushfire

Share of the suburb AREA covered by bushfire-prone designation. Area, not properties — and the two differ a lot. Belmont North is 45.72% by area but 23.62% by property count, because designated land is not evenly built on. If you want "what share of homes here are affected", which is the figure our own reports headline, use `GET /v1/suburbs/{suburb_name}/risks/property-hazard-counts` — it returns a count and pct per hazard against the suburb's actual dwellings.

suburbs_risks_capital_growth_impact

Matched-study capital-growth impact (%/yr) for bushfire, flood, contamination, mine subsidence, aircraft noise and surface acid sulfate, scaled by the share of properties affected.

suburbs_risks_counts

Counts of contamination points, heritage items and erosion-prone polygons inside the suburb.

suburbs_risks_extras

Landslide / storm-tide coverage, EPA notices, landlord-insurance medians and crime benchmark, with per-mesh-block detail.

suburbs_risks_flood

Share of the suburb AREA covered by modelled flood overlays. Area, not properties. For the share of DWELLINGS affected — the figure our own reports headline — use `GET /v1/suburbs/{suburb_name}/risks/property-hazard-counts`. To answer **where** the flood zone is, pass `geojson=true`. The response then includes the actual modelled flood polygons clipped to the suburb boundary, suitable for a street map, plus truncation/simplification metadata. Do not infer street location from `coverage_pct` alone.

suburbs_risks_heritage_share

Shown in the suburb report as the 'Heritage' card in the Risks section. Share of the suburb's properties inside a heritage polygon.

suburbs_risks_hv_power_lines

Shown in the suburb report as the 'High-voltage power lines' card in the Risks section. Whether high-voltage transmission lines cross the suburb, how many, and the highest voltage class (overhead lines only).

suburbs_risks_property_hazard_counts

Counts and shares of the suburb's properties flagged bushfire / flood / mine-subsidence / contamination / aircraft-noise / acid-sulfate.

suburbs_risks_slope

Shown in the suburb report as the 'Steep terrain' card in the Risks section. Median / 90th-percentile property gradient and share of steep (>10°) properties.

suburbs_sales_recent

Shown in the suburb report as the 'Recent sales' table tab in the Properties section. Properties sold in the suburb, with beds/baths/land size, sale price and date, and coordinates, newest sale first. **Default:** the last 3 years, one row per property (its most recent sale). **Full history:** pass `from` and/or `to` (YYYY-MM-DD) for every sale in that range — one row per sale, so a property sold twice appears twice. History depth varies by state: NSW from 2001, Victoria, Queensland, WA and SA from about 2010, Tasmania from about 2014, ACT and NT from 2019. Paginated with `limit`/`offset`: `total` reports how many sales match (counted before paging) and `next_offset` is the offset of the next page (null on the last one). Order is stable — newest first, ties broken by property — so paging never repeats or skips a sale. Each page is one call, at a flat price regardless of page size.

suburbs_sales_summary

Number of sales and median sold price in the suburb over the last 3 years.

suburbs_schools_all

Shown in the suburb report as the 'Schools' card in the Lifestyle section. Schools for a suburb: which public catchments cover it, and which schools sit nearby regardless of zone, with NAPLAN rank, sector, level and attendance for each. Catchments answer "where would my child be guaranteed a place"; nearby answers "what else is within reach".

suburbs_schools_catchment

Shown in the suburb report as the 'Schools' map layer (the catchment toggle) in the Lifestyle section. Public-school catchment polygons covering the suburb.

suburbs_schools_nearby

Shown in the suburb report as the 'Schools' card and table in the Lifestyle section. Schools serving / near the suburb, with rank + attendance data.

suburbs_shapes_boundary

Simplified SAL boundary polygon (GeoJSON Feature) plus centroid.

suburbs_shapes_busy_roads

Shown in the suburb report as the 'Busy roads (noise)' map layer in the Risks section. Busy-road line segments clipped to the suburb — the report's road-noise exposure proxy.

suburbs_shapes_easements

Shown in the suburb report as the 'Easements' map layer (explorer) in the Risks section. Registered easement geometries intersecting the suburb (GeoJSON FeatureCollection).

suburbs_shapes_hazards

Hazard polygons for one layer, clipped to the suburb boundary (empty collection = hazard not present).

suburbs_shapes_mesh_blocks

2021 mesh-block polygons covering the suburb (GeoJSON FeatureCollection, mesh-block code per feature).

suburbs_shapes_neighbours

Neighbouring suburbs as a GeoJSON FeatureCollection — each with its boundary polygon and distance in km.

suburbs_shapes_noise_heatmap

Shown in the suburb report as the 'Noise level' map layer (the 'Noise' card) in the Risks section. Precomputed noise colour regions clipped to the suburb, plus cell-centre heat points.

suburbs_shapes_public_housing_sa1

Shown in the suburb report as the 'Public housing' card and map layer in the Risks section. SA1 polygons in the suburb with their 2021 public-housing share (only SA1s above 0%).

suburbs_similar

Shown in the suburb report as its 'Similar Suburbs' section. Top-10 suburbs ranked closest by our similarity model.

suburbs_street_forecasts

Shown in the suburb report as the 'Street Profile' table in the Market section. 2/4/8-year price forecasts for every street in the suburb, anchored to the real sold median. Unpaged by default. Large suburbs are large — Point Cook has 943 streets (~1.4 MB) — so pass `limit`/`offset` when you don't need the lot. `total` reports how many exist. Flat price per call regardless of page size.

properties

properties_amenities_nearby

Shown in the property report as the 'Amenities' card and map layer in the Lifestyle section. Curated amenities (supermarkets, green spaces, restaurants/cafes) within `radius_m` of the property, bucketed and nearest-first. **Price: 10¢ per call.**

properties_basics_all

The physical facts about a dwelling in one call: bedrooms, bathrooms, parking spaces, dwelling type (house, unit, townhouse and so on) and land area in square metres. Priced as the sum of the five individual calls. Ask for a single field instead if that is all you need. **Price: 23¢ per call.**

properties_basics_bath_count

Bathroom count from the latest matching listing. **Price: 5¢ per call.**

properties_basics_bed_count

Bedroom count from the latest matching listing. **Price: 5¢ per call.**

properties_basics_dwelling_type

Dwelling type (house, unit, townhouse, ...). **Price: 5¢ per call.**

properties_basics_land_area_sqm

Shown in the property report as the 'Land area' figure in the 'Lot & subdivision' card in the Valuation part of the Market section. Parcel land area in square metres from the cadastral feed. **Price: 3¢ per call.**

properties_basics_parking_count

Parking-space count from the latest matching listing. **Price: 5¢ per call.**

properties_comparables_all

The evidence a valuer or agent would use to price this property: a CMA comparable set, the single closest comparable sale, and recent sales nearby. Use it to answer "what did similar homes around here actually sell for", and to show the working behind a valuation rather than a bare number. **Price: 74¢ per call.**

properties_comparables_cma_comp_set

Shown in the property report as the 'Comparable sales' part of the Market section. Top comparable sales used to triangulate the subject property's value. **Price: 60¢ per call.**

properties_comparables_cma_single_comp

Single best comparable from the CMA set (highest dist_score). **Price: 10¢ per call.**

properties_comparables_recent_sales_nearby

Shown in the property report as the 'Recent sales' table tab in the Properties section. Recent comparable sales in a small radius around the subject parcel. **Price: 4¢ per call.**

properties_context_mesh_blocks

Mesh-block polygons within 1 km of the property (GeoJSON), each with avg annual growth, investor counts, modal street and median sold price. **Price: 30¢ per call.**

properties_context_nearby_for_sale

Shown in the property report as the 'For sale' table tab in the Properties section. Currently for-sale listings within `radius_km` of the property (newest first, max 30) with AVM and rent-yield comparison. **Price: 20¢ per call.**

properties_context_street_bedroom_series

Shown in the property report as the '{N}-bed {type} median' card in the Valuation part of the Market section. The subject's bedroom band (bed count from listing history) and the suburb's 10-year price series for that band. **Price: 15¢ per call.**

properties_development_all

What the planning scheme allows on this block: its zoning code and every planning overlay that touches it (heritage, flood, bushfire, height and so on, as published by the council). Answers "can I build on it, and what is restricted". Development applications in the surrounding area are a suburb-level call. **Price: 8¢ per call.**

properties_development_zoning_code

Shown in the property report as the 'Zoning' card in the Development section. Primary zoning at the property's point — code (R2, B4, ...) when the council ships one, plus the human-readable name and the broader category. **Price: 3¢ per call.**

properties_development_zoning_overlays

Development overlays intersecting the property's parcel. **Price: 5¢ per call.**

properties_history_all

Shown in the property report as the 'Property History' card in the Overview section. Everything we hold on what this property has sold and rented for: the full sale history and the full rent history, each with its most recent record called out separately. This is the expensive one in the Property - History family, because it returns complete series rather than a latest figure. For "what did it last sell for", call `/sale-history-latest` instead. **Price: 80¢ per call.**

properties_neighbours

Shown in the property report as the 'Meet the neighbours' map in the Overview section. Adjoining-parcel neighbours, enriched with address + property type + bed/bath/garage from the latest matching listing. **Price: 30¢ per call.**

properties_profile

Resolve a GNAF to its full statistical geography hierarchy (mesh block → SA1 → SA2 → SA3 → SA4 → GCCSA → State) plus the parallel admin chain (LGA, suburb (SAL), postcode). Call this once to get every geography key the rest of the data layers index on. **Price: 3¢ per call.**

properties_rent_history

Shown in the property report as the 'Property History' card in the Overview section. All For Rent records, most-recent first. **Price: 30¢ per call.**

properties_rent_history_latest

Most-recent For Rent record. **Price: 10¢ per call.**

properties_risks_all

Shown in the property report as its 'Risks' section. Every property-level risk overlay in one call. Flat 30¢ — may grow without increasing the bundle price as new overlays are added. With ``?geojson=true`` each risk that has a polygon overlay also carries its 1km-radius-clipped `geojson` FeatureCollection + `geojson_meta`. **Price: 48¢ per call.**

properties_risks_bushfire

Shown in the property report as the 'Bushfire' card in the Risks section. Bushfire-prone-area overlays within 1 km. Read `on_property` — a returned row means "found nearby", not "this property is in a bushfire zone". **Price: 15¢ per call.**

properties_risks_environment

Environmental-risk overlay (contamination, salinity, ...). **Price: 3¢ per call.**

properties_risks_erosion

Shown in the property report as the 'Coastal erosion' card in the Risks section. Coastal / soil erosion overlays within 1 km. Read `on_property` — a returned row means "found nearby", not "this property is eroding". **Price: 3¢ per call.**

properties_risks_flood

Shown in the property report as the 'Flooding' card in the Risks section. Modelled flood overlays within 1 km. Read `on_property` — a returned row means "found nearby", not "this property floods". **Price: 10¢ per call.**

properties_risks_heritage

Shown in the property report as the 'Heritage' card in the Risks section. Heritage-listing overlays within 1 km. Read `on_property` — a returned row means "found nearby", not "this property is heritage-listed". **Price: 3¢ per call.**

properties_risks_historical_flood

Shown in the property report as the 'Flooding' card in the Risks section. Recorded historical flood extents within 1 km. Read `on_property` — a returned row means "found nearby", not "this property flooded". **Price: 3¢ per call.**

properties_risks_hv_power_line

Shown in the property report as the 'High-voltage power lines' card in the Risks section. High-voltage power-line easement near the parcel. **Price: 2¢ per call.**

properties_risks_landslide

Shown in the property report as the 'Landslide risk' card in the Risks section. Landslide-risk overlays within 1 km. Read `on_property` — a returned row means "found nearby", not "this property is at landslide risk". **Price: 3¢ per call.**

properties_risks_mobile_black_spot

Mobile-coverage black-spot overlay near the parcel. **Price: 2¢ per call.**

properties_risks_public_housing

Shown in the property report as the 'Public housing' card in the Risks section. Public-housing concentration overlay near the parcel. **Price: 4¢ per call.**

properties_sale_history

Shown in the property report as the 'Property History' card in the Overview section. All Sold + For Sale records, most-recent first. **Price: 30¢ per call.**

properties_sale_history_latest

Shown in the property report as the 'Property history and current listing status' card in the Valuation part of the Market section. Most-recent Sold or For Sale record. **Price: 10¢ per call.**

properties_schools_all

Shown in the property report as the 'Schools' card in the Lifestyle section. Schools for this address: the ones nearby with their distances, and how each ranks on NAPLAN alongside sector, level and attendance. The priciest bundle in the Property family, because it joins the school register, the ranking table and distance calculations. Call `/schools/nearby` alone if rankings do not matter. **Price: 105¢ per call.**

properties_schools_nearby

Shown in the property report as the 'Schools' card and table in the Lifestyle section. Schools within ~5km of the property, with rank + student counts. **Price: 5¢ per call.**

properties_schools_ranking

Schools within ~5km of the property, ranked by NAPLAN / socioeconomic score. **Price: 100¢ per call.**

properties_street_profile

Shown in the property report as the 'Street Profile' table in the Market section. The property's own street: current median price, 2/4/8-year price forecasts, realised growth, sale/rental turnover, renter share and houses/units on the street — plus the suburb-wide medians to judge it against and the street's rank on 4-year forecast growth. 404s when the street has no forecast row rather than falling back to suburb-wide figures, which would answer a different question. **Price: 20¢ per call.**

properties_surroundings_listing_history_signals

Shown in the property report as the 'Meet the neighbours' map colouring in the Overview section. Latest sold/rent dates and likely-owner-status signal per nearby property. **Price: 20¢ per call.**

properties_surroundings_parcels

Shown in the property report as the 'Meet the neighbours' map parcels in the Overview section. Cadastral parcel polygons (GeoJSON) for properties around the subject. **Price: 25¢ per call.**

properties_surroundings_properties

Shown in the property report as the 'Meet the neighbours' map pins in the Overview section. Every GNAF property within 200 m of the subject, with lat/lng and mesh block. **Price: 15¢ per call.**

properties_surroundings_public_housing

Shown in the property report as the 'Public Housing' map legend in the Overview section. Properties around the subject flagged by the public-housing classifier. **Price: 15¢ per call.**

properties_surroundings_tenure

Shown in the property report as the 'Housing Tenure' card in the Demographics section. Tenure shares — owned outright, mortgaged, rented, public housing — for each mesh block around the subject. **Price: 15¢ per call.**

properties_transport_nearby

Nearest train / tram / bus / ferry stop to the property, per mode, with distance. Widen `radius_m` for the nearest station beyond 1km. **Price: 5¢ per call.**

properties_valuation_agent_quoting

Shown in the property report as the 'Agent quoting accuracy' card in the Valuation part of the Market section. Quoting accuracy of the property's current listing agency — cohort, median guide-vs-sold deviation, underquote rate and its 5 most-recent tracked sales. Only while the property is listed for sale with a tracked agency. **Price: 50¢ per call.**

properties_valuation_land_values

Council land valuations for the parcel — val_2021..val_2025 series with YoY change and $/sqm, plus lot area and zoning description. **Price: 15¢ per call.**

properties_valuation_negative_gearing

Shown in the property report as the 'Budget 2026 exposure' card in the Valuation part of the Market section. Negative-gearing stat at the finest available level: per-property cashflow scenarios (80% + 105% LVR), falling back to mesh-block then suburb investor-exposure. **Price: 20¢ per call.**

economics

economics_cash_rate

The Reserve Bank's current cash rate target, when it took effect and the last move. The RBA publishes the cash rate free of charge on its website; the attribution says so, as the RBA's terms require. **Price: 1¢ per call.**

economics_cash_rate_series

The cash rate target over time, oldest first. `decisions` lists every change with its size in basis points; `monthly` gives one value per month, for charts and joins against other monthly series. **Price: 1¢ per call.**

economics_cpi

Consumer Price Index: the index number with its period and annual % change, one row per quarter or month. Covers all groups, the underlying measures (trimmed mean, weighted median), the 11 expenditure groups, and the housing components property people ask about — rents, new dwellings, property rates, maintenance, utilities, electricity and insurance — for the eight capitals and Australia. Coverage follows the published CPI: quarterly is national for every item (all groups from 1948) plus all groups for each capital; monthly has every item for Australia and each capital (most from 2024; rents from 2022; new dwellings and property rates from 2017). A combination the publisher does not publish returns `available: false`. **Price: 2¢ per call.**

economics_cpi_adjust

Move a dollar amount between two periods using the CPI — e.g. a 2021 median into today's dollars, or a past rent by the rents index. The frequency follows the period format. **Price: 1¢ per call.**

economics_cpi_latest

The latest CPI reading for Australia and each capital city — index, and period and annual % change. **Price: 1¢ per call.**

economics_series

Every economic series we hold — national statistics and the RBA — with its latest value. Use it to find a `series_id`, then fetch the history from `/economics/series/{series_id}`. Datasets: `cpi` (25 items incl. rents and new dwellings, 8 capitals + national, monthly and quarterly), `cash-rate`, `mortgage-rates` (banks' indicator rates), `wpi` (wages), `building-approvals` (states + capital cities), `housing-lending` (owner-occupier, investor, first home buyers), `population`, `labour-force` and `dwelling-transfers` (median prices and counts by capital city). **Price: 1¢ per call.**

economics_series_history

One series' observations (oldest first) with its metadata and the publisher's attribution. Optional `from` / `to` narrow the range; omit both for the full history (CPI goes back to 1948). **Price: 2¢ per call.**

area

area_stats_fields

Discover which statistical fields exist. Free (0c). Fuzzy, token-based matching covers table topics and clean column labels as well as terse field codes. Common natural-language plurals and synonyms are handled, so the verbatim `query=couples with children` discovers the exact 2021 family-composition count fields rather than substituting the broader `census_family_households` metric. Use the returned field code(s) with the priced `/area-stats/SAL/{suburb}/values` route. ~17k fields available. **Free.**

area_stats_regions

List the regions that exist at a level — every suburb, LGA, postcode, etc. Free (0c). Use it to discover the exact region names to pass to /values. **Free.**

area_stats_values

Statistical field values for one region. Pass `fields` — 1 to 5 field codes (from /fields) — to fetch. At SAL level, `mode=sa1` switches from the suburb-aggregate value to a per-SA1 breakdown — every SA1 that falls inside the suburb, each with its own values. **Price: 3¢ per call.**

lga

lga_list

All Australian LGAs. Optional `?state=` filter (e.g. 'NSW'). Returns `{lga, state}` per row. Flat cost. **Price: 1¢ per call.**

lga_population

Shown in the suburb report as the council-area lines on the 'Population' chart in the Demographics section. The estimated resident population for the LGA at 30 June each year from 2001, with the change on the year before. Accepts the names `/lga/list` returns. **Price: 5¢ per call.**

lga_profile

LGA's parent chain — state + GCCSA. LGAs aren't strictly nested in SA4 so the upward chain stops there. **Price: 3¢ per call.**

geocode

geocode_address

Resolve a freeform address string to candidate GNAF identifiers. Use this before calling any ``/v1/properties/{gnaf_id}/...`` route — those endpoints require a GNAF in the path. Returns up to 10 candidates, ranked by Meilisearch score. **Price: 1¢ per call.**

geocode_suburb

Autocomplete a partial suburb search string against the official suburb (SAL) list. Use this before calling ``/v1/suburbs/{name}/...`` — those endpoints require a canonical SAL name in the path. **Free.**

mbs

mbs_list

Mesh-block codes inside a suburb. ``sal`` is required for now — nationwide / by-LGA / by-SA3 listings will land later when there's a story for the large payloads (a single LGA can hit a few thousand mesh blocks). **Price: 3¢ per call.**

mbs_profile

The mesh block's upward geography chain — SA1, SA2/3/4, GCCSA, state — plus the parallel admin chain (LGA, suburb (SAL), postcode). **Price: 3¢ per call.**

sa4

sa4_list

All Australian SA4s. Optional `?state=` filter. Returns `{sa4, state}` per row. Flat cost. **Price: 1¢ per call.**

sa4_profile

SA4's parent chain — GCCSA + state. **Price: 3¢ per call.**

me

The calling account and its current prepaid balance, in cents. **Free.**

ping

ping

Returns immediately if the API is up. No authentication required and not metered — safe to poll from a load balancer, uptime monitor, or status dashboard without affecting your usage. **Free.**

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

ping_head

removed 22 Sep 2026

get_series_v1_economics_series

removed 5 Nov 2026

properties_valuation_all

removed 6 Nov 2026

properties_valuation_avm

removed 6 Nov 2026

properties_valuation_value_series

removed 6 Nov 2026

Endpoints

URL	Transport	State	Latency	Checked
https://api.microburbs.com.au/mcp	streamable-http	answering	1015 ms	15 min ago

Alternatives to Microburbs Australian Property Data

same job, measured the same way

PropertyData

by co-propertydata

UK property data: prices, rents, valuations, sold prices, planning, flood risk, titles and UPRNs.

answering

Domain MCP by UnClick

by malamutemayhem

Australian property listings, prices, and suburb stats from Domain. By UnClick.

41 installs/wk local only

Daleads MCP

by resuly

Australian development application and property intelligence data for AI agents.

136 installs/wk local only

Research

by co-propbar

UK property research tools - crime stats, schools, demographics, valuations for AI.

answering

HouseData

by housedata

UK property data: EPC, flood risk, planning, sale prices, MEES 2030 checks and grants.

11 tools answering

CaLesVaut

by calesvaut

Is this listing too expensive? French property sales (DVF), crime, rents, risks, schools

11 tools answering

Zertidox

by zertidox

Spanish official certificates, property valuations and legal documents, with request tracking.

3 tools answering

DwellDelta - Australian rent check and property indicators

by com-dwelldelta

Australian and NZ rents by area, NSW sale prices and a local rent check, for AI agents.

1 297 installs/wk 7 tools answering

Microburbs Australian Property Data — questions

Answers built from our own checks of this server.

What can Microburbs Australian Property Data do?

It exposes 200 tools, read directly from the server on our last check. Among them: area_stats_fields, area_stats_regions, area_stats_values, economics_cash_rate, economics_cash_rate_series, economics_cpi and 194 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Microburbs Australian Property Data mostly used for?

Its tools cluster around suburbs, properties and economics. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Microburbs Australian Property Data working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1032 ms. The bar chart above shows every period we have measured.

Did Microburbs Australian Property Data ever remove tools?

Yes. ping_head, get_series_v1_economics_series, properties_valuation_all, properties_valuation_avm and 1 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect Microburbs Australian Property Data?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Microburbs Australian Property Data need an API key?

No. Microburbs Australian Property Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 200 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Microburbs Australian Property Data?

It answers our handshake in 1032 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.