Location infrastructure for developers
Search places, resolve addresses, render boundaries, standardize records, and connect geographic data.
One foundation
for geographic products.
Mapbase is built on five core primitives — locations, boundaries, addresses, postcodes and canonical IDs. They power every layer above them, from data to UI blocks.
Locations
Normalized places across administrative and local levels — countries, regions, provinces, cities, parishes — resolved consistently across Portugal, Spain and Italy.
Boundaries
Geographic shapes for regions, cities, zones and other territorial units. Query them as GeoJSON, render them anywhere.
Addresses
Structured address records for lookup, matching and enrichment. Parsed components in, canonical address out.
Postcodes
Postal code data connected to real places and hierarchies. Not a flat list — a graph of codes, locations and boundaries.
Canonical IDs
Stable identifiers that let your systems reference geography consistently across teams, products and time.
Composed the way
you build products.
API-first
Every primitive is designed to be queried, resolved, linked and composed.
Canonical by default
Stable IDs and normalized structures instead of fragile text matching.
Composable
Mix data primitives, UI components, SDK helpers and higher-level blocks.
Built for products
Search, CRMs, analytics, logistics, real estate, internal tools, user-facing apps.
One API
for geographic products.
UI components
for location products.
Reusable primitives for search, selection, display and exploration. Ship location-aware interfaces without rebuilding them from scratch.
Search inputs
Autocomplete for places, addresses, postcodes and canonical entities.
Boundary viewers
Render places and regions visually inside maps and geographic UIs.
Hierarchy pickers
Navigate structured territorial levels cleanly.
Address selectors
Guide users from free text to normalized structured records.
Location cards
Display canonical place metadata in a consistent format.
Bring Mapbase data into your interface with components designed for real implementation, not demos.
Explore components→Higher-level
building blocks.
Blocks combine APIs, SDK logic and UI patterns into ready-to-use product workflows — so you ship recurring geographic problems without reinventing the glue.
Place autocomplete
Search and select canonical places.
Address resolution
Convert user input into structured address entities.
Boundary lookup
Find and return the geographic unit behind a point, place or ID.
Postcode resolver
Connect postal codes to their underlying geographic entities.
Territory selector
Let users define, browse and assign geography through structured boundaries.
Entity explorer
Inspect relationships between places, addresses, postcodes and IDs.
Blocks help you skip the repetitive glue code and ship full geographic workflows faster.
Browse blocks→Built on Postgres
+ PostGIS
Fast geospatial infrastructure, exposed through a minimal Hono API.
Typed end-to-end
Zod contracts → OpenAPI 3.1 → @mapbase/types.
Docs that humans and machines can use
Scalar at /reference, raw spec at /openapi.json, Markdown for LLMs.
LLM-ready documentation
Full API reference in Markdown for agents, codegen, embeddings, or internal tooling.
No SDK lock-in
Just REST, GeoJSON, curl, and fetch.
Trusted across the Mediterranean.
We dropped our home-grown Iberian address normaliser for /v1/addresses. Freed up a quarter of engineering work.
Marta Silva
Head of Data, Habitarium


