Parcelgps Catastro GPS API
63
AI ReadinessAI-Aware (B-)63/100
Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey9 EndpointsREST
For Agents
Find the cadastral parcel for an address or a GPS point in Spain and other European countries, look up a parcel by reference, list the units in a building, and read its terrain and ground-motion data.
Use for: Find the cadastral reference for Calle Mayor 10, Madrid, Get the parcel at latitude 40.4168 and longitude -3.7038, Retrieve the boundary and area of a parcel from its reference, List all units in this building in Valencia
Not supported: Does not calculate routes, render map tiles, or value properties. Use for cadastral parcel lookups by address, coordinates, or reference in Spain and other European countries only.
The Catastro GPS API turns addresses and coordinates into cadastral parcels for Spain and 25 other European countries, returning the parcel reference, its GPS point, outline polygon, and area. It looks up a parcel or unit by cadastral reference, finds the parcel at a WGS84 point, ranks address candidates, and for Spain resolves structured or free-text addresses through the live Catastro street index. Spanish data comes from Parcel GPS's own copy of the Dirección General del Catastro with live Catastro as a fallback, and further operations list every unit of a finca and report a parcel's terrain, protected areas, climate normals, and ground motion in millimetres per year.
Install Jentic One Beta
Connect the Catastro GPS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Catastro GPS API, 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%2Fparcelgps.com%2Fparcelgps" | 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%2Fparcelgps.com%2Fparcelgps" | 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.
Capabilities
What an agent can do with Catastro GPS API.
Resolve an address to ranked parcel candidates in Spain and 25 other European countries through /api/search/address/candidates
Find the parcel at a WGS84 point with lat and lng, or latitude and longitude in a JSON body
Look up a parcel or unit by cadastral reference with /api/catastro/{refcat} and get its outline and area
List all dwellings, shops, garages, and storage units of a finca by its 14-character reference
Resolve a Spanish address from provincia, municipio, nombreVia, and numero, or from free text in direccion, against the live Catastro street index
Read a parcel's relief, protected areas, and climate normals, and its 2020 to 2024 ground motion in mm per year
Use Cases
Patterns agents use Catastro GPS API for, with concrete tasks.
★ Agent property lookups through Jentic
A real-estate assistant agent receives an address from a client and needs the official parcel. Through Jentic it calls searchAddressCandidates with the address, picks the top candidate, and then getParcel for the outline and area, citing the Dirección General del Catastro attribution returned with Spanish data. Your own Jentic One instance injects the X-API-Key value, so the agent never holds it.
GET /api/search/address/candidates with country 'ES' and q 'Calle Mayor 10, Madrid', then GET /api/catastro/{refcat} for the first candidate and report its superficieParcela
Field and drone work by coordinates
Surveyors, insurers, and agricultural teams often start from a GPS point rather than an address. GET /api/search/coordinates with lat and lng, or the POST form with latitude and longitude, returns the parcel at that point, and the terrain operation adds relief, protected areas, and climate normals for the same reference.
GET /api/search/coordinates with lat 39.4699 and lng -0.3763, then GET /api/catastro/{refcat}/terrain for the returned reference
Building units and ground motion checks
Property due diligence needs both what is in a building and whether the ground beneath it moves. GET /api/catastro/{refcat14}/units lists every dwelling, shop, garage, and storage unit of a finca with cursor paging, and GET /api/catastro/{refcat}/ground-motion reports subsidence or uplift in millimetres per year for 2020 to 2024.
GET /api/catastro/{refcat14}/units for reference '9872023VH5797S', then GET /api/catastro/{refcat}/ground-motion for the same reference and report the yearly movement
Key Endpoints
9 endpoints — the catastro gps api turns addresses and coordinates into cadastral parcels for spain and 25 other european countries, returning the parcel reference, its gps point, outline polygon, and area.
METHOD
PATH
DESCRIPTION
GET
/api/search/address/candidates
Address to ranked parcel candidates
GET
/api/search/coordinates
Parcel at a WGS84 point
GET
/api/catastro/{refcat}
Parcel or unit by cadastral reference
GET
/api/catastro/{refcat14}/units
All units of a finca
POST
/api/search/address/parse
Free-text Spanish address to reference
GET
/api/catastro/{refcat}/ground-motion
Parcel ground motion 2020 to 2024
GET
/api/search/address/candidates
Address to ranked parcel candidates
GET
/api/search/coordinates
Parcel at a WGS84 point
GET
/api/catastro/{refcat}
Parcel or unit by cadastral reference
GET
/api/catastro/{refcat14}/units
All units of a finca
POST
/api/search/address/parse
Free-text Spanish address to reference
GET
/api/catastro/{refcat}/ground-motion
Parcel ground motion 2020 to 2024
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Catastro GPS API
- AI-Aware (B-)63/100
99
Foundational Compliance68
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability50
Security47
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
68
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
5%
Example Density
How richly the API is illustrated with examples.
96%
Example Validity
Percentage of examples that conform to their schemas.
69%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
41%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
48%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
47
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D+Signals: 1
47%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Catastro GPS by hand means the X-API-Key header, a unit-based monthly quota with per-key rate limits, and picking between European candidate search and the Spanish live Catastro operations. Through Jentic you install once, import Catastro GPS from the API Directory, store the key once, and your agent calls it.
Permission scoping
Catastro GPS puts the cadastral reference in the URL path, as in /api/catastro/{refcat}/terrain, so a rule can pin your agent to one parcel. You choose which of the nine read and search operations it may call, which also bounds how many units it can spend.
Credential isolation
Your Catastro GPS API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find the parcel at these coordinates' or 'look up a cadastral reference', and Jentic returns the matching Catastro GPS operation with its input schema so the agent sends the right fields.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Catastro GPS API through Jentic.
What authentication does the Catastro GPS API use?
The Catastro GPS API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec; keys are created in the developer portal. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
What are the rate limits for the Catastro GPS API?
The spec sets limits per API key and minute by plan: Free 10, Developer 60, Startup 120, and Growth 300 requests per minute, with monthly quotas of 250, 5,000, 15,000, and 50,000 units. Going over the per-minute limit returns 429 with code KEY_RATE_002 and a Retry-After header.
Which countries does the Catastro GPS API cover?
Address candidate search covers Spain and 25 other European countries, and every covered country returns the parcel reference, GPS point, outline, and area by reference and by coordinates unless the spec's coverage table says otherwise. The structured and free-text address operations resolve Spanish addresses only, against the live Catastro street index.
How do I find a parcel from an address through Jentic?
Install Jentic One, add the Catastro GPS API from the Jentic API Directory, and store your API key once. Your agent searches for 'find the cadastral parcel for an address', gets searchAddressCandidates with its input schema, and calls it with country and q. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Catastro GPS MCP server?
You don't need an MCP server to give your agent the Catastro GPS API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.
Can I limit what my agent is allowed to do with the Catastro GPS API?
Yes. Write a rule that allows only the address candidates and coordinate search operations, and your agent can locate parcels but cannot spend units on unit listings, terrain, or ground-motion reports. Your own Jentic One instance logs what it called, which helps you track quota use.
GET STARTED