Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
LINZ Data Service (BYOK) icon

LINZ Data Service (BYOK)

Search New Zealand land and geospatial datasets on the LINZ Data Service, read layer details and run point queries with your own API key

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderLINZ Data Serviceunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Search LINZ Data Service for datasets about parcel boundaries
Tools called
search_catalog
List LINZ polygon layers tagged with topographic
Tools called
list_layers
Show details of LINZ layer 50772
Tools called
get_layer
Which categories exist in the LINZ Data Service?
Tools called
list_categories
Which licences are used on LINZ data?
Tools called
list_licenses
What is the SRID of NZGD2000 New Zealand Transverse Mercator in LINZ Data Service?
Tools called
list_coordinate_systems

About

LINZ Data Service (BYOK) lets an AI assistant read your own LINZ Data Service data through the LINZ Data Service API with a key you supply (LINZ Data Service API key). Read-only: 7 tools (search_catalog, list_layers, get_layer, list_categories, list_licenses, list_coordinate_systems, query_vector_layers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to data.linz.govt.nz. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINZ Data Service. LINZ Data Service and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the LINZ Data Service API (data.linz.govt.nz) with a BYOK key; documentation: https://apidocs.koordinates.com/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • Search catalogSearch the whole LINZ Data Service catalogue (layers, tables, sets, documents and more) by text, kind, category or tag.
  • List layersList published layers and tables with id, title, type, publication dates and thumbnail, filtered by text, category, tag or geometry type.
  • Get layerGet the full details of one layer or table: description, category, tags, licence, data summary, versions and download counts.
  • List categoriesList the catalogue categories with their slug, URL key and sub-categories, for use as the category filter.
  • List licensesList the licences used by catalogue items with id, title, type, jurisdiction, version and link.
  • List coordinate systemsList coordinate systems known to the service (id, name, kind, units and SRID), optionally filtered by name text or kind.
  • Query vector layersFind features of one or more vector layers near a WGS84 point, nearest first, within a radius in metres.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-linzdataservice.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-linzdataservice.connectorbay.com/mcp
RESTPOST https://byok-linzdataservice.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-linzdataservice.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your LINZ Data Service API key in the X-Upstream-Key header (get one at www.linz.govt.nz).
  • Ask a question; the agent picks the right tool and answers from the live data.

LINZ Data Service connector: questions and answers

What is the LINZ Data Service connector?

LINZ Data Service (BYOK) lets an AI assistant read your own LINZ Data Service data through the LINZ Data Service API with a key you supply (LINZ… It is a hosted MCP server with 7 tools such as Search catalog, List layers, Get layer, List categories, List licenses, List coordinate systems, published by Unify Dynamics LLC. It is independent and not affiliated with LINZ Data Service.

How do I connect LINZ Data Service to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-linzdataservice.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-linzdataservice.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-linzdataservice.json.

Do I need a LINZ Data Service account or API key?

Yes: this is a bring-your-own-key connector. Create a LINZ Data Service API key at https://www.linz.govt.nz/guidance/data-service/linz-data-service-guide/web-services/creating-api-key and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is LINZ Data Service read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the LINZ Data Service connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

GoatCounter (BYOK)

Read your GoatCounter privacy-friendly web analytics: page views per path, referrers, browsers, systems and locations with BYOK

Live · MCP + REST8 tools

GoDaddy Domains (BYOK)

Read your GoDaddy domains, DNS records, domain availability and name suggestions through the Domains v3 API with BYOK

Live · MCP + REST6 tools

Golioth (BYOK)

Read your Golioth IoT devices, logs, firmware releases, artifacts, cohorts and OTA update events with your own project API key

Live · MCP + REST12 tools

Golioth RPC (BYOK)

Look up your Golioth projects and devices and call confirmed remote procedures on a device with your own project API key

Live · MCP + REST4 tools

GoSquared (BYOK)

Read your GoSquared web analytics: real-time visitors, pages, sources and countries plus historical trends with your own API key

Live · MCP + REST12 tools

Grafana Cloud (BYOK)

Read your Grafana Cloud dashboards, folders, data sources, alert rules, annotations and teams with BYOK

Live · MCP + REST10 tools

Documentation

Back to top

LINZ Data Service (BYOK) — connector documentation

  • MCP endpoint: https://byok-linzdataservice.connectorbay.com/mcp
  • REST API: POST https://byok-linzdataservice.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-linzdataservice.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own LINZ Data Service LINZ Data Service API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-linzdataservice.connectorbay.com/health · Tool schemas: https://byok-linzdataservice.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-linzdataservice · agent@connectorbay.com

What LINZ Data Service (BYOK) is for

LINZ Data Service (BYOK) lets an AI assistant read your own LINZ Data Service data through the LINZ Data Service API with a key you supply (LINZ Data Service API key). Read-only: 7 tools (search_catalog, list_layers, get_layer, list_categories, list_licenses, list_coordinate_systems, query_vector_layers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to data.linz.govt.nz. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINZ Data Service. LINZ Data Service and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Search LINZ Data Service for datasets about parcel boundaries"
  • "List LINZ polygon layers tagged with topographic"
  • "Show details of LINZ layer 50772"
  • "Which categories exist in the LINZ Data Service?"
  • "Which licences are used on LINZ data?"
  • "What is the SRID of NZGD2000 New Zealand Transverse Mercator in LINZ Data Service?"

What it does

  • search_catalog: Search the whole LINZ Data Service catalogue (layers, tables, sets, documents and more) by text, kind, category or tag.
  • list_layers: List published layers and tables with id, title, type, publication dates and thumbnail, filtered by text, category, tag or geometry type.
  • get_layer: Get the full details of one layer or table: description, category, tags, licence, data summary, versions and download counts.
  • list_categories: List the catalogue categories with their slug, URL key and sub-categories, for use as the category filter.
  • list_licenses: List the licences used by catalogue items with id, title, type, jurisdiction, version and link.
  • list_coordinate_systems: List coordinate systems known to the service (id, name, kind, units and SRID), optionally filtered by name text or kind.
  • query_vector_layers: Find features of one or more vector layers near a WGS84 point, nearest first, within a radius in metres.

BYOK key

You bring your own LINZ Data Service LINZ Data Service API key (https://www.linz.govt.nz/guidance/data-service/linz-data-service-guide/web-services/creating-api-key). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to data.linz.govt.nz over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the LINZ Data Service API (data.linz.govt.nz) with a BYOK key; documentation: https://apidocs.koordinates.com/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINZ Data Service. LINZ Data Service and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your LINZ Data Service account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

LINZ Data Service (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What LINZ Data Service (BYOK) is. LINZ Data Service (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own LINZ Data Service data: Search New Zealand land and geospatial datasets on the LINZ Data Service, read layer details and run point queries with your own API key. You bring your own LINZ Data Service LINZ Data Service API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one LINZ Data Service call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to data.linz.govt.nz, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If LINZ Data Service rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What LINZ Data Service receives. The request we make on your behalf, including the key and the arguments, under LINZ Data Service's own terms and privacy policy. LINZ Data Service acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer LINZ Data Service gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your LINZ Data Service data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. LINZ Data Service (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at LINZ Data Service at any time to end all access.

Children. LINZ Data Service (BYOK) is a general-audience service operated by the adult using the assistant, under LINZ Data Service's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

LINZ Data Service (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the LINZ Data Service (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. LINZ Data Service (BYOK) provides: Search New Zealand land and geospatial datasets on the LINZ Data Service, read layer details and run point queries with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own LINZ Data Service credentials and only access data you are allowed to access. LINZ Data Service's terms apply to your use of LINZ Data Service; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINZ Data Service. LINZ Data Service and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data LINZ Data Service returns, lightly trimmed; it may be incomplete, delayed or changed by LINZ Data Service. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your LINZ Data Service account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent LINZ Data Service's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; LINZ Data Service may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your LINZ Data Service key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action LINZ Data Service takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-linzdataservice

LINZ Data Service (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. LINZ Data Service (BYOK) never asks for them.

Get LINZ Data Service (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own LINZ Data Service LINZ Data Service API key. Create one at https://www.linz.govt.nz/guidance/data-service/linz-data-service-guide/web-services/creating-api-key, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to LINZ Data Service. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with LINZ Data Service.