PDOK APIs for AI Agents
Maps GeolocationMappingJentic-Generated DocumentsNo authAgent Ready
For Agents
APIs3 in catalogue
Endpoints215 indexed
AuthNo auth — 1 credential for all 3 APIs
ProvenanceJentic-generated documents
An agent can query Dutch government geospatial datasets across PDOK, retrieving habitat distribution polygons for Natura 2000 areas, mussel and oyster bank survey features from the Wadden Sea, and surface water body line and polygon geometry for Water Framework Directive reporting. All queries are read-only spatial feature retrieval over public open data.
PDOK is the official source for Dutch national geospatial open data, so its datasets carry regulatory weight for EU Habitats Directive and Water Framework Directive work rather than being crowd-sourced approximations. The three APIs here share the same open-access, no-key model and Dutch-named feature endpoints, making them a coherent set for environmental and ecological spatial analysis in the Netherlands.
PDOK API Catalog
3 APIs across 1 product group. All share one credential.
Maps Geolocation3
Habitatrichtlijn verspreiding van habitattypen WFSQuery geographic distribution data for EU Habitats Directive habitat types across Dutch Natura 2000 areas.~208 endpointsOppervlaktewaterlichamenQuery Dutch surface water body geometry as lines and polygons for Water Framework Directive compliance.~4 endpointsMossel- en oester habitatsQuery mussel and oyster bank habitat survey data from Dutch Wadden Sea tidal flats.~3 endpoints
Which PDOK API should I use?
| I want to... | Use |
|---|---|
| Terrestrial habitat type distribution for Natura 2000 sites | Habitatrichtlijn verspreiding van habitattypen WFS |
| Marine shellfish habitat data | Mossel- en oester habitats |
| Surface water body geometry for water management | Oppervlaktewaterlichamen |
Install Jentic One Beta
Connect the PDOK APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PDOK APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpdok.nl" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpdok.nl" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “Dutch government geospatial data for habitats and water bodies”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these PDOK services by hand means learning each dataset's Dutch-named feature endpoints and matching habitat types, water body geometries, and shellfish surveys to their own paths, even though the services are open and need no key. Once Jentic One is installed, you or your agent can find and add any of these PDOK APIs from the Jentic directory to your workspace and call them with no credential to manage.
Permission scoping
All operations across these PDOK services are read-only spatial queries, and each carries the feature id in the URL path, so your own rules in Jentic One can pin an agent to a specific dataset or feature collection and allow only the operations you choose to run.
Credential isolation
These PDOK services are public open data and need no authentication, so there is no credential to store; for any API that does need one, your own Jentic One instance holds credentials encrypted rather than exposing them to the agent.
Intent-based discovery
Agents search the Jentic directory by intent, such as 'Dutch habitat distribution' or 'surface water body polygons', and Jentic returns the matching Dutch-named PDOK operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using PDOK APIs through Jentic.
What kind of data do the PDOK APIs provide?
They provide Dutch national geospatial open data as spatial features. Across the three APIs you can query terrestrial habitat type distributions for Natura 2000 areas, mussel and oyster bank habitats on Wadden Sea tidal flats, and surface water body line and polygon geometry for water management.
Do any of the PDOK APIs require authentication or an account?
No. All three are public Dutch government open data services with no API keys, tokens, or accounts. Every endpoint is freely accessible, so an agent can query them without any credential setup.
Why does Jentic publish OpenAPI specs for these PDOK services?
PDOK does not publish OpenAPI specifications for these services. Jentic generates and maintains them so agents and developers can call the datasets through structured tooling, and each spec is validated against the live service and kept up to date.
What regulatory frameworks do these datasets support?
The habitat distribution WFS supports EU Habitats Directive Article 17 reporting for Natura 2000 areas, the surface water body dataset is the spatial foundation for the EU Water Framework Directive in the Netherlands, and the shellfish habitat survey supports Dutch fisheries and marine conservation reporting.
Can I combine data from more than one PDOK API in a single workflow?
Yes. Because the APIs share the same open-access model and cover complementary environmental themes, an agent can overlay habitat distributions, water body geometry, and shellfish habitat features together for combined ecological and regulatory analysis.
What spatial data format do the responses use?
The services return spatial feature data compatible with GeoJSON, including geometry as points, lines, or polygons plus attribute fields describing classification and reporting metadata, ready for import into GIS software or spatial databases.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.