Planning Data API · Australia
A planning data API that covers seven states, not one.
Zone, overlays, development controls and a stated confidence level for any Australian address — one REST call, or an MCP tool your agent calls directly.
Yes — there is an API for Australian planning data covering every mainland state and territory except the NT. Feasibly returns the zone, the overlays affecting a parcel, the development controls that apply and how far each value can be trusted, for roughly 455 councils across VIC, NSW, SA, QLD, WA, the ACT and TAS. Most alternatives cover one state, or three.
What the API covers, state by state
| State | Councils | What comes back | Depth tier |
|---|---|---|---|
| Victoria | 79 councils | Zone schedules read and verified by a person from the source planning scheme, plus ResCode Clause 55 envelope | Verified schedule |
| New South Wales | 128 councils | LEP zone, height, FSR and lot size via the Standard Instrument APIs, plus DCP dwelling controls codified for 116 councils | API + machine-extracted DCP |
| South Australia | 74 councils | Planning & Design Code zones, overlays and technical numeric variations from the state API | State API |
| Queensland | 11 councils | Council planning-scheme endpoints, QDC MP1.1 envelope, state heritage register | State/council API |
| Western Australia | 136 councils | SLIP zones and overlays, R-Codes (SPP 7.3) residential design codes | State API |
| ACT | 1 territory | Territory Plan 2023 zones, 9 districts, 118 precinct overrides, Design Guide envelope | Territory API |
| Tasmania | 29 councils | theLIST zones and overlays against the Tasmanian Planning Scheme | State API |
Depth is deliberately not uniform, and the response says which tier produced each value rather than presenting them as equivalent. The Northern Territory is not covered: it publishes no working spatial API, and we would rather omit a jurisdiction than guess it.
How reliable is the data the API returns?
Every response carries rules_confidence and an overlay array where empty
means checked-and-clear, never unknown — a distinction most planning data drops, and the
one that turns a failed hazard query into a false all-clear. Amendments are monitored
daily across all seven states. If a lookup returns the wrong zone, that lookup is free
and we add 10 credits, on every tier.
Australian planning data API — common questions
Is there an API for Australian planning data across every state?
Yes. Feasibly returns zone, overlays, planning rules and a stated confidence level for an address in seven states and territories — Victoria, New South Wales, South Australia, Queensland, Western Australia, the ACT and Tasmania — from a single REST call or MCP tool. That is roughly 455 councils. The Northern Territory is not covered, because it publishes no working spatial API.
Which states does the Feasibly planning API cover?
VIC (79 councils), NSW (128), SA (74), WA (136), TAS (29), QLD (11 councils via council endpoints) and the ACT. Coverage depth is not uniform and the response says which tier each answer came from, so an integration can branch on it rather than assume.
Does the API return DCP or planning-scheme controls, or only the zone?
Both, and it labels which. Victorian responses carry council-specific zone schedules verified from the source scheme. NSW carries LEP controls from the state API plus dwelling controls (setbacks, site coverage, landscaped area, private open space) codified from council DCPs for 116 councils, at machine-extracted confidence. Other states return zone, overlays and the controls their statewide instrument sets.
How is this different from calling the state government APIs directly?
The government APIs are per-state, differently shaped, and several are geo-fenced or unreliable. Feasibly normalises all seven into one response contract, adds the council-level controls that no state API publishes, monitors amendments daily and states a confidence level per value. An empty overlay array means checked-and-clear, never unknown.
Can an AI agent call it directly?
Yes. Feasibly runs a hosted MCP server, published in the official MCP registry, so Claude, ChatGPT, Cursor or any MCP client can call the same eight tools a REST client uses. There is also an llms.txt, an agent-skills index and markdown content negotiation on every page.
What happens if the API returns the wrong zone?
That lookup is refunded and we add 10 credits, on every tier including free. The claim is made from inside the product and every claim becomes a dataset correction. We publish the guarantee because a planning answer nobody will stand behind is not worth integrating.
Try it against a real address
Screen an address free with no signup, or read the endpoint reference and be calling it in a few minutes.
Screen an address →Endpoints and parameters: API reference · Quickstart · Use it from Claude · Full coverage detail · Pricing