Hosted MCP coming soon. v1 data: mazowieckie.Join the waitlist
landfeed
Menu
Use with Claude Use with ChatGPT API and docs Data and sources Use cases Pricing How we keep it true Join waitlist

Use cases

Built for agents
that answer about land.

Four kinds of teams, one envelope. Each workflow below uses only the six tools and the contract rules on this site.

01 · CRM and listing vendors

Paste what the client typed.

You are adding an assistant to a CRM or listing portal. The feature is "paste what the client typed, get the parcel and a verdict with citations"; the record comes with it.

  1. Pass the text as typed

    Your assistant calls check with q set to the client's words, typos and all. No resolve step.

  2. Handle ambiguity honestly

    If status is ambiguous, show the candidates or ask which obręb when needs_obreb is true. Re-call with the chosen id.

  3. Show the verdict with its sources

    Render each check's result, source.attribution and as_of. Quote note where a layer is not covered.

  4. Answer follow-ups from the record

    The full record is embedded in the check result, so the next question needs no further call.

Why it fits

One request per answer keeps model cost and latency flat. Every response says what it cost in billing, and outside loaded data the call is refunded.

Caching, embedding and keeping answers in session memory are allowed with attribution.

02 · Professionals in Claude or ChatGPT

Ask in the chat you already use.

Architects, surveyors, agents and buyers' advisers who work inside Claude or ChatGPT add the connector once and ask about parcels in plain language.

  1. Add the connector

    Once, with the hosted MCP URL. Claude or ChatGPT steps.

  2. Ask about the planning

    The agent calls layer with planning: plan ogólny zone and status with effective_from, MPZP status and symbol where published, WZ possibility, and the gmina's planning status.

  3. Check the constraints

    Flood, landslide, protected areas and road access come back in the same check, each with its source.

  4. Read what is not covered

    Where the state does not publish an input machine-readably, the check says unknown. The agent tells you, rather than guessing.

Not legal advice

Checks are booleans with sources, the same way a flood flag is. They are a fast first read, not a wypis or an opinion.

03 · Banks and insurers

Know what changed.

You hold collateral or insured property across many parcels and need to know when a plan, a permit, a flood map or the parcel itself changes.

  1. Baseline the portfolio

    POST /v1/parcel/batch takes up to 1,000 ids per call, one request per item, and returns every layer with its hash and version.

  2. Ask for changes

    events returns changes since a date, newest first: plan ogólny or MPZP status, WZ possibility, flood map revision, landslide or protected-area change, new building, subdivision or retirement, permit nearby.

  3. Trace each change

    Each event carries before, after, the source and as_of.

What to know today

History starts with the first precompute run in October 2026; an empty list for an earlier period means no history, not no change. Push delivery (webhooks) is planned for v1.1; monitoring is planned to be quoted per parcel per month.

04 · PV and wind siting

Area in, parcels with flags out.

You screen land for solar or wind. You need the parcels in an area and the reasons each one is out.

  1. List parcels in the area

    search with a bbox up to 4 km², or around a point with a radius up to 2,000 m, paginated with a cursor.

  2. Read the exclusion layers

    For each parcel, parcel with layers narrowed to what you screen on: plan ogólny zone, protected areas, flood, and soil class where the powiat publishes it.

  3. Keep the unknowns visible

    Soil class is not_covered where the powiat does not publish it; keep those parcels in a separate list instead of passing them.

Not promised yet

Distance to grid connection points is not promised until URE data is ingested. Utilities attributes and noise come later.

Start with
one call.

v1 covers mazowieckie. Join the waitlist to hear when the hosted MCP opens.

Join the waitlistAPI and docs