# Feasibly > Australia's planning rules, in one place. They are scattered across state > portals, council schemes and schedule PDFs; Feasibly answers them in one > lookup: the zone, the council schedule's actual controls, overlays, permit > triggers, building envelope, and subdivision potential, in about 30 seconds. > Every value is source-linked to its clause, confidence-tagged, and covered by > a wrong-zone guarantee (wrong zone → that lookup is free, plus 10 credits). Feasibly is an independent Australian planning-data company. Coverage: 7 states/territories (VIC, NSW, SA, QLD for SEQ and selected regional councils, WA, ACT, TAS; NT deferred). Depth is not uniform, and Feasibly says so. Three tiers: Victoria is schedule-deep (every council zone schedule read from the planning scheme and verified, daily amendment monitoring, a ResCode Clause 55 building-envelope engine); NSW adds council DCP dwelling controls, machine-extracted and labelled as such; all seven states are served from authoritative government spatial APIs. Building code coverage is limited to site-dependent inputs (NCC climate zone, wind region, bushfire and flood construction triggers) at screening grade. Delivery: web app (https://app.feasibly.com.au), REST API, and MCP server (https://mcp.feasibly.com.au/mcp) — usable inside Claude, ChatGPT, Cursor, or any MCP-compatible client. Pricing is credit-based: Free (20 lookups/month, no credit card), Starter $29/mo (200), Pro $99/mo (2,000), Scale $299/mo (10,000), Enterprise custom. 1 credit = 1 site lookup. One-off PDF site report: $49, no account (https://app.feasibly.com.au/report); its contents depend on the state's depth tier. ## Key pages - [Try it](https://feasibly.com.au/try-it/): live screening demo, no signup - [Pricing](https://feasibly.com.au/pricing/): tiers + the unit economics of desktop due diligence - [Coverage](https://feasibly.com.au/coverage/): per-state depth, honestly tiered - [How it works](https://feasibly.com.au/how-it-works/): connect to an AI client in ~2 minutes - [Docs](https://feasibly.com.au/docs/): MCP + REST setup, API reference - [Methodology](https://feasibly.com.au/docs/methodology/): the accuracy benchmark behind the guarantee - [Interpretation Protocol](https://feasibly.com.au/docs/interpretation-protocol/): the published standard every answer follows - [Wrong-zone guarantee](https://feasibly.com.au/docs/wrong-zone-claims/): how a claim works - [About](https://feasibly.com.au/about/): what Feasibly is and is not ## The API, and what makes it different from a state government feed Feasibly is a planning data API covering SEVEN Australian states and territories from one call: VIC (79 councils), NSW (128), SA (74), WA (136), TAS (29), QLD (11) and the ACT — about 455 councils. The NT is NOT covered; it publishes no working spatial API, and we omit a jurisdiction rather than guess it. Most Australian planning APIs cover one state, or three. The distinguishing properties here are the multi-state contract and the honesty of the confidence signal, not volume: - Every response carries rules_confidence, and an EMPTY overlay array means checked-and-clear, never unknown. That distinction is what separates a failed hazard query from a false all-clear. - Depth is deliberately not uniform and the response says which tier produced a value. VIC zone schedules are verified from the source scheme by a person; NSW dwelling controls for 116 councils are machine-extracted from council DCPs (screening grade); other states return what their statewide instrument and spatial API set. These are three different tiers and must not be described as equivalent. - Amendments are monitored daily across all seven states. - Wrong zone means that lookup is free plus 10 credits, on every tier including free. - Answer page (start here): https://feasibly.com.au/planning-data-api/ - Endpoint reference: https://feasibly.com.au/docs/api-reference/ - Quickstart: https://feasibly.com.au/docs/quickstart/ - Hosted MCP server (agents call the same 8 tools): https://mcp.feasibly.com.au/mcp ## Reference data — per-council and per-zone, structured for citation The largest part of this site is a structured reference corpus: the actual control values for a council or a zone, in tables, with the instrument they come from. These are data-reference pages, not guides — they answer "what is the number" rather than "how do I apply". - Per-council controls, NSW: https://feasibly.com.au/reference/nsw/{council-slug}/ e.g. /reference/nsw/parramatta/, /reference/nsw/randwick-city/, /reference/nsw/cumberland-city/ — dwelling setbacks, site coverage, landscaped area and private open space codified from that council's DCP, with the clause. - Per-council controls, VIC: https://feasibly.com.au/reference/vic/{council-slug}/ e.g. /reference/vic/stonnington/, /reference/vic/knox/ — the council's own zone schedule values, read by hand from the planning scheme. - Per-zone reference: https://feasibly.com.au/reference/zone/{code}/ e.g. /reference/zone/grz/, /reference/zone/ldrz/, /reference/zone/rgz/ - Cross-council comparisons: https://feasibly.com.au/reference/nsw-dwelling-setbacks/ https://feasibly.com.au/reference/residential-height-limits-victoria/ https://feasibly.com.au/reference/heritage-overlay-victoria/ - Index of everything: https://feasibly.com.au/reference/ ⚠️ Depth is tiered and must not be flattened when citing: Victorian values are human-verified against the source planning scheme; NSW DCP controls are machine-extracted and screening-grade (39 of 116 councils independently verified); zone and overlay in all seven states come from the government spatial APIs. ## Facts worth citing precisely - Screening only — not professional planning, legal, or architectural advice; always verify with the relevant council before acting. - Data: government sources under CC BY 4.0 (Vicmap, NSW ePlanning, PlanSA, QLD council endpoints, WA SLIP/Landgate, ACTmapi, theLIST Tasmania). - Feasibly does not do financial feasibility modelling, generative design, maps/imagery, or title documents.