How it works

Address in. Planning data out. In seconds.

Feasibly is an MCP server. Plug it into your AI client (Claude, ChatGPT, Cursor) and ask about any Australian property.

It runs inside the AI client you already use (Claude, ChatGPT, Cursor), so there's no SDK and nothing new to learn. The LLM stops fabricating planning data and starts citing the authority it came from.

2 minutes to connect · 8 seconds per lookup · 7 states

The flow

Three steps. About two minutes.

Most operators are screening their first site within two minutes of registering. The longest part is choosing which AI client to connect.

S. 01

Get a free API key.

Sign up at app.feasibly.com.au with email (no credit card). Your key arrives instantly. Free tier gives you 20 lookups a month, every month.

S. 02

Add Feasibly to your AI client.

For MCP-compatible clients (Claude Desktop, Claude.ai, ChatGPT Developer Mode, Cursor, Windsurf), paste the connection URL with your key: https://mcp.feasibly.com.au/mcp?key=YOUR_KEY. The walkthrough for each client is in the docs.

S. 03

Ask about any Australian address.

"What's the zone of 12 Smith Street, Brunswick VIC?" The LLM calls Feasibly, returns structured data (zone, schedule, overlays, building envelope, source URL) in 8 seconds. Source-linked, confidence-tagged, audit-ready.

Inside one lookup

Six hops, one answer, every value traceable.

This is what happens between your address and your answer, and where each number comes from. Nothing is inferred by a language model.

  1. 01

    Address

    12 Smith St, Brunswick VIC

    Your input
  2. 02

    Geocode

    Rooftop point, not street centreline

    G-NAF Verified
  3. 03

    Parcel

    Lot boundary, area, frontage, corner status

    State cadastre Verified
  4. 04

    Zone

    GRZ1, point-in-polygon, not a postcode guess

    Government spatial API Verified
  5. 05

    Schedule

    Min lot 300 m² · height 11 m, the council's own numbers, which differ between two GRZ1 sites

    Cl.32.08-3 · council schedule Verified (VIC) Machine-extract (NSW/QLD DCP)
  6. 06

    Overlays & envelope

    HO148 heritage · permit triggered · setbacks and garden area

    Overlay schedules + ResCode Verified

A layer that fails is reported, never silently cleared. If the bushfire service is unreachable, you get data gap, not “not affected”.

What you get back

Structured data, not prose.

Every Feasibly response is the same shape: structured fields with a confidence tag and a source URL. The LLM can reason over it; you can paste it into a Section 32.

From source

Government APIs only.

Vicmap, NSW EPI, SA PlanSA, QLD council endpoints, WA SLIP, ACTmapi, theLIST. We don't guess and we don't infer.

Council-specific

620+ schedules codified.

VIC schedules manually read into structured rules. Min lot, height, garden area, coverage: the council's actual values, not the VPP default.

Tagged + linked

Confidence on every value.

verified_schedule, verified_vpp_default, or unverified_vpp_default. Every parameter cites the source URL it came from, so you can check any number against the scheme yourself.

Behind the scenes

Built on infrastructure that doesn't break.

Cloudflare-edge worker, MCP Streamable HTTP transport, Durable Object state, KV-backed auth. ~150ms typical response time. Daily VIC amendment monitor catches scheme changes within 24 hours of gazettal.

  • Cloudflare edge, ~150ms response, SYD primary
  • MCP + REST, both transports, same data
  • Daily monitor, gazettal alerts within 24h
  • Wrong-zone guarantee: refund + 10 bonus credits + dataset correction

Connect once. Screen everywhere.

Free tier. No credit card. 20 lookups per month, every month.

If we get the zone wrong, that lookup is free and we credit ten more.