LIM ReportIndependent website

Not a LIM. Open council and LINZ data, explained. Details

For agents — machine access

This site publishes a machine door: an agent can read the dataset without guessing the page.

Machine access8/9

This is not a badge: every line points to the file that proves it, and the only missing one is listed too.

This report as JSON

End-to-end example

The code belmont, taken from this register's real sample. An agent connected to the MCP server sends:

POST https://mcp-registres.cloudflare33-7aa.workers.dev/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"resolve_code","arguments":{"registre":"LIM Report — Auckland zoning and hazards","code":"belmont"}}}

and receives this record:

suburb_slugbelmont
suburbBelmont
local_boardDevonport-Takapuna
addresses1810
main_zoneResidential - Mixed Housing Suburban Zone
tsunami_evacuation_share0.2 %
pagehttps://lim-report.pages.dev/auckland/belmont/

Without the server: FNV-1a 32-bit of belmont, modulo 31, gives 0 — the record is in /e/0.json, on the line starting with that code.

Example computed when the site is generated, from a real row — no value is written by hand.

The files

Tools/api/v1/tools.json
Manifest/api/v1/manifest.json
Extract/api/v1/echantillon.json

Tools served

Reserved

These paths exist and answer statut: reserve. ⚠️ They say what is missing instead of returning a 404.

⚠️ The HTML pages and the tools that read them are free and stay free. Only the built layer — reconciliation, linkage, history — can be charged for.

The service level, and its limit

Regulation (EU) 2023/138 requires Member States to publish certain datasets — so-called high-value — free of charge, machine-readable, with an API and bulk download. We apply that service level to everything we publish, including what the law does not require.

⚠️ This register is not presented as a high-value dataset in the legal sense. It is a service level we impose on ourselves, not a regulatory guarantee — and bulk download stays free at the official source, which is named on this site.

One MCP server for the whole portfolio

This register's tools are callable over MCP under its name, from a single entry point: https://mcp-registres.cloudflare33-7aa.workers.dev/mcp. A client adds one connector and gets all published registers, not just this one.

⚠️ Without that server this register's resolver would be mute to the outside: an agent would have to reimplement our hash function to know which fragment to read. ⛔ And a remote MCP server is added by hand in the client: it makes this register callable, not findable. How to use it.

This register is listed in the catalogue registres.pages.dev.