Australian planning intelligence
Zone. Schedule. Overlays. Building envelope. Subdivision potential.
Eight tabs, a council schedule PDF and an unbilled hour. Or one lookup, source-linked to its clause and confidence-tagged. Not scraped. Not guessed.
✓ No credit card · 20 free lookups/month · ✓ Underwritten accuracy guarantee
Built on official government planning data, not scraped listings
Licensed under Creative Commons Attribution 4.0 · every value source-linked to its clause
The lookup
The zone code is a pointer. Feasibly returns the numbers that actually govern the site: each one carries its source clause and a confidence tier you can check.
The old way
Every screen used to mean the same ritual: the map viewer for the zone, the scheme PDF for the schedule, separate searches for overlays and amendments, then hoping none of it changed last month. The numbers that decide the site live four clicks deep. Feasibly collapses the ritual into one answer.
The ritual · ~8 minutes per site
One lookup · 30 seconds
Why professionals trust it
Every value shows where it came fromCl.32.08-3 and how sure we are✓ verified.
Two GRZ1 sites in two councils can have different minimum lot sizes. Scraped tools hide that. In Victoria, Feasibly reads the council schedule (620+ of them, by hand) and monitors daily for amendments.
Depth varies by state, and we say so. Victoria is schedule-deep; NSW adds machine-extracted DCP controls for 116 councils; every state runs on authoritative government APIs. See coverage, tiered honestly →
Works where you work
Feasibly is a data layer, not another portal to log into. The same schedule-resolved answer: on the web, over the API, or straight inside your AI assistant.
Web app
Type an address
Zone, schedule, overlays and envelope on one screen. PDF report when you need to send it.
app.feasibly.com.au →REST API
Screen your pipeline
One POST per site, or batch 20 at once. Structured JSON your stack can build on.
API reference →MCP server
Ask your AI client
Plug into Claude, ChatGPT or Cursor in about two minutes. Your assistant answers with our citations, not its guesses.
Setup guides →The proof
SQM Architects, a practising Australian architecture firm, runs its client feasibility work on Feasibly every day. Real projects, not a demo. If a schedule is wrong, it gets hit on a live project before you ever see it.
“Every feasibility triage at SQM starts with the same lookup, the same citations, the same guarantee any Feasibly customer gets. There’s no special version for us: if the data’s wrong, our projects hit it first.”
— SQM Architects · practising firm & production validation environment
Built for site screeners
Same engine, different first question. Pick yours.
Conveyancers
Zone, overlays, heritage and flood on a sale property, answered before the client finishes asking.
→Surveyors
Schedule min lot size, frontage and planning context, before you quote the plan.
→Small developers
Screen 20 candidate sites in an afternoon. Spend due-diligence budget on the three that survive.
→Building designers
Start every sketch from the real envelope: height, setbacks, garden area, site coverage.
→Architects
Clause-cited envelope figures you can put straight into a design response.
→Planning consultants
Triage “can my client subdivide this” in 30 seconds, before you quote the hour.
→Valuers, buyers’ agents, PropTech: see all professionals →
The underwrite
Every claim becomes a permanent dataset correction, published in the changelog. The price you pay is the price of verified data, not best-effort.
See the unit economics: the old way vs Feasibly → · How a claim works →
Before you ask
No, and we’re precise about that. Feasibly is the screening layer you run before the professionals: it tells you which sites are worth a planner’s desktop review, a surveyor’s quote, an architect’s sketch. Always verify with the relevant council before acting on a screen.
Seven states and territories, ~455 councils. Depth is tiered, and we label it honestly: Victoria is schedule-deep, with 620+ council schedules read by hand and monitored daily; NSW adds machine-extracted DCP dwelling controls for 116 councils, flagged screening-grade; every state runs on authoritative government spatial APIs. Full coverage map →
The zone call. If a lookup returns the wrong zone, that lookup is free and we credit ten more. The claim also becomes a permanent dataset correction in our public changelog. Every other value carries a confidence tier instead of a promise, so you always know which numbers are verified and which are screening-grade. How a claim works →
Portals show you which controls apply and link you to the scheme. Feasibly reads the schedule and returns the numbers (min lot size, height, setbacks, garden area), each with its clause and a confidence tier. Many teams run both. Feasibly vs Landchecker →
Yes. Feasibly ships as an MCP server: connect it to Claude, ChatGPT, Cursor or any MCP-compatible client in about two minutes, and your assistant answers planning questions with clause citations instead of guesses. There’s a REST API when you’d rather integrate directly. Setup guides →
20 lookups a month, every month: full responses, not teasers. No credit card. Want to test it before creating an account? Run a live screen right now, no signup.
Free tier. No credit card. 20 lookups a month, every month.
or try it live first · no account needed
If we get the zone wrong, your lookup is free and we credit ten more.
Questions before you start? Talk to a human: a real reply, usually under 24 hours.