Overture Maps Foundation
Overture Maps Foundation is a Linux Foundation collaborative project that produces free, open, and interoperable map data. Overture publishes cloud-native GeoParquet datasets, on a regular release cadence, across six themes - Addresses, Base, Buildings, Divisions, Places, and Transportation - governed by a common conflation pipeline and an open schema. Rather than a hosted REST API, Overture distributes data through Amazon S3 and Microsoft Azure (and via partner mirrors on BigQuery, Snowflake, Databricks, Fused, Wherobots), and provides an open Python CLI, a tile generator, and an Explorer site for developers. Founding members include Amazon, Meta, Microsoft, and TomTom.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Overture Maps Foundation the way a machine reads it — 15 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Overture Maps Foundation scores 20.1/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Overture Maps Foundation
Each block below is one kind of artifact we hold for Overture Maps Foundation. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Overture Addresses Theme
Open dataset of global address points and ranges, released as cloud-native GeoParquet alongside the other Overture themes.
Overture Base Theme
Open dataset of base map features - land cover, water, land use, infra - released as cloud-native GeoParquet to serve as a foundation for map rendering.
Overture Buildings Theme
Open dataset of global building footprints with attributes (heights, classes, sources), released as cloud-native GeoParquet.
Overture Divisions Theme
Open dataset of administrative and statistical boundaries (countries, regions, counties, localities, neighborhoods) released as cloud-native GeoParquet.
Overture Places Theme
Open dataset of global points of interest - businesses, landmarks, and services - released as cloud-native GeoParquet with categories, addresses, and confidence scoring.
Overture Transportation Theme
Open dataset of the global road and transportation network (segments and connectors) released as cloud-native GeoParquet, suitable for routing and analytics.
Overture Schema
Canonical open schema specification for all Overture themes, maintained in the OvertureMaps/schema GitHub repository and versioned with each data release.
Overture Data Releases
Repository of release notes, cloud paths (Amazon S3 and Microsoft Azure), and access scripts for every Overture data release. Datasets are distributed as cloud-native GeoParquet...
Overture Maps Python CLI
Open-source Python command-line tool and library for downloading and querying Overture data. Maintained at OvertureMaps/overturemaps-py.
Overture Explorer
Interactive web explorer for browsing and inspecting Overture features across themes and releases.
Overture Tiles
Open tile-generation tooling that builds vector tilesets from Overture data for rendering and downstream applications.
Scroll within the panel for all 11 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Overture Maps Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Overture Maps Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Overture Maps Foundation — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/overture-maps · machine-readable index on apis.io