Google Maps Platform
Google Maps Platform offers APIs and SDKs for maps, routes, and places functionality.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Google Maps Platform the way a machine reads it — 302 machine-readable artifacts across 41 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 — Google Maps Platform scores 65.8/100 (strong), with a separate agent-readiness read of 74/100 (agent native). 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.
How we profile Google Maps Platform
Each block below is one kind of artifact we hold for Google Maps Platform. 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 41
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.
Maps SDK for Android
Add maps to Android and Wear OS applications with customizable markers, polylines, and user interaction support.
Maps SDK for iOS
Add maps to iOS applications with automatic server access, map display, and gesture handling.
Google Maps for Flutter
Add Google Maps to Flutter applications across Android, iOS, and web platforms.
Navigation SDK for Android
Integrate Google Maps turn-by-turn navigation into Android applications with UI customization and route configuration.
Navigation SDK for iOS
Integrate Google Maps turn-by-turn navigation into iOS applications with UI customization and route configuration.
Navigation for Flutter and React Native
Add Google Maps turn-by-turn navigation to cross-platform Flutter and React Native applications.
Places API
Access information about places using HTTP requests including search, details, and autocomplete.
Places SDK for Android
Access rich place information including names, addresses, ratings, and photos in Android applications.
Places SDK for iOS
Access rich place information including names, addresses, ratings, and photos in iOS applications.
Distance Matrix API
Calculate travel distance and time for multiple origins and destinations.
Roads API
Snap GPS coordinates to roads and find speed limits.
Routes API
Compute routes and route matrices with real-time traffic, replacing Directions and Distance Matrix APIs.
Route Optimization API
Assign tasks and routes to a vehicle fleet, optimizing against objectives and constraints for transportation goals.
Maps Static API
Embed a Google Maps image on a web page using a simple HTTP request with no JavaScript required.
Maps Embed API
Place an interactive map or Street View panorama on a web page with a simple HTTP request and no JavaScript required.
Street View Static API
Embed a non-interactive Street View panorama or thumbnail into a web page using a simple HTTP request.
Maps URLs
Launch Google Maps and initiate actions like search, directions, or map display using cross-platform URL schemes.
Elevation API
Return elevation data for locations on the earth or sampled elevation data along paths.
Geolocation API
Determine device location using cell tower and Wi-Fi access point data.
Time Zone API
Retrieve time zone information for coordinates on the earth including UTC offset and daylight savings data.
Address Validation API
Validate and standardize addresses, returning deliverability verdicts, geocodes, and address component details.
Aerial View API
Create and display photorealistic 3D aerial view videos rendered using Google geospatial imagery.
Map Tiles API
Provide high-resolution Photorealistic 3D Tiles, 2D Tiles, and Street View Tiles for immersive map visualizations.
Maps Datasets API
Upload, manage, and serve custom geospatial datasets for use with Google Maps Platform.
Places Aggregate API
Compute statistical insights and aggregate data about places within a specified area.
Places Insights
Query places data in BigQuery to derive statistical insights for site selection, market analysis, and business intelligence.
Air Quality API
Request air quality data for a specific location including air quality indexes, pollutants, and health recommendations.
Pollen API
Deliver location-specific pollen data including pollen types, plant species, pollen index, and health recommendations.
Solar API
Access solar potential data for hundreds of millions of buildings worldwide including building insights and data layers.
Weather API
Provide comprehensive weather information including temperature, precipitation, wind, cloud cover, and forecasts for locations worldwide.
Street View Insights
Analyze Google Street View imagery data to derive insights about the location and condition of public assets.
Imagery Insights API
Query and classify street-level imagery to extract actionable intelligence from real-world visual observations.
Roads Management Insights
Analyze route-based trip duration and speed data for managing road networks and transportation infrastructure.
Google Earth
Access Google Earth geospatial data and imagery analysis capabilities for developers.
Google Maps Platform Autocomplete API
Get place predictions based on text input
Google Maps Platform Directions API
Route computation between origin and destination
Google Maps Platform Geocoding API
Forward and reverse geocoding operations
Google Maps Platform Nearby Search API
Search for places near a specific location
Google Maps Platform Photos API
Access photos associated with places
Google Maps Platform Place Details API
Get detailed information about a specific place
Google Maps Platform Text Search API
Search for places using a text query
Scroll within the panel for all 41 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Google Maps Directions API
OPEN COLLECTIONGoogle Maps Geocoding API
OPEN COLLECTIONGoogle Maps Places API (New)
OPEN COLLECTIONArazzo Workflows 6
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Google Maps Enrich a Postal Address into a Full Place Record
Geocode an address to a place ID, then use that place ID to pull the full Places record.
ARAZZOGoogle Maps Resolve Two Addresses and Route Between Them
Geocode a start and end address, then compute directions between the resolved place IDs.
ARAZZOGoogle Maps Autocomplete a Place and Close the Session with Details
Run a session-tokened autocomplete request, then fetch details for the chosen prediction using the same session token.
ARAZZOGoogle Maps Find the Nearest Open Place and Route to It
Search for places near a coordinate ranked by distance, verify the nearest is operational, then route the user there.
ARAZZOGoogle Maps Search for a Place and Assemble a Place Card
Text search for a place, read its full details, then fetch a photo URI for rendering.
ARAZZOGoogle Maps Reverse Geocode a Coordinate and Discover What Is Around It
Turn raw coordinates into a street address, then list the points of interest surrounding that point.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
google-maps-mcp.yml
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Google Maps Platform GraphQL Schema
This document describes a conceptual GraphQL schema for the Google Maps Platform APIs, covering Maps, Routes, Places, Geocoding, Elevation, Geolocation, Address Validation, Road...
GRAPHQLPricing 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.
Google 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.
Google Maps Finops
FINOPSFeatures 17
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 17 ·
Semantic Vocabularies 4
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Google Maps Context
JSON-LDGoogle Maps Places Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Google Maps Platform API Rules
SPECTRALGoogle Maps Platform API Rules
SPECTRALJSON Schema 99
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessibilityOptions
JSON SCHEMAAddressComponent
JSON SCHEMAAuthorAttribution
JSON SCHEMAAutocompleteRequest
JSON SCHEMAAutocompleteResponse
JSON SCHEMABounds
JSON SCHEMACircle
JSON SCHEMABounds
JSON SCHEMADirectionsResponse
JSON SCHEMAFare
JSON SCHEMAGeocodedWaypoint
JSON SCHEMALatLng
JSON SCHEMALeg
JSON SCHEMAPolyline
JSON SCHEMARoute
JSON SCHEMAStep
JSON SCHEMATextValuePair
JSON SCHEMATimeZoneTextValue
JSON SCHEMATransitDetails
JSON SCHEMATransitLine
JSON SCHEMATransitStop
JSON SCHEMADirectionsResponse
JSON SCHEMAFare
JSON SCHEMAFormattableText
JSON SCHEMAGoogle Maps Geocode Result
JSON SCHEMAGeocodedWaypoint
JSON SCHEMAAddressComponent
JSON SCHEMABounds
JSON SCHEMAGeocodingResponse
JSON SCHEMAGeocodingResult
JSON SCHEMAGeometry
JSON SCHEMALatLng
JSON SCHEMAPlusCode
JSON SCHEMAGeocodingResponse
JSON SCHEMAGeocodingResult
JSON SCHEMAGeometry
JSON SCHEMALatLng
JSON SCHEMALeg
JSON SCHEMALocalizedText
JSON SCHEMALocationBias
JSON SCHEMALocationRestriction
JSON SCHEMAOpeningHours
JSON SCHEMAParkingOptions
JSON SCHEMAPaymentOptions
JSON SCHEMAPeriod
JSON SCHEMAPhoto
JSON SCHEMAPhotoMedia
JSON SCHEMAGoogle Maps Place
JSON SCHEMAPlaceAddressComponent
JSON SCHEMAPlacePrediction
JSON SCHEMAAccessibilityOptions
JSON SCHEMAAuthorAttribution
JSON SCHEMAAutocompleteRequest
JSON SCHEMAAutocompleteResponse
JSON SCHEMACircle
JSON SCHEMAFormattableText
JSON SCHEMALatLng
JSON SCHEMALocalizedText
JSON SCHEMALocationBias
JSON SCHEMALocationRestriction
JSON SCHEMAOpeningHours
JSON SCHEMAParkingOptions
JSON SCHEMAPaymentOptions
JSON SCHEMAPeriod
JSON SCHEMAPhotoMedia
JSON SCHEMAPhoto
JSON SCHEMAPlaceAddressComponent
JSON SCHEMAPlacePrediction
JSON SCHEMAPlace
JSON SCHEMAPlusCode
JSON SCHEMAPoint
JSON SCHEMAQueryPrediction
JSON SCHEMARectangle
JSON SCHEMAReview
JSON SCHEMASearchNearbyRequest
JSON SCHEMASearchPlacesResponse
JSON SCHEMASearchTextRequest
JSON SCHEMAStructuredFormat
JSON SCHEMASuggestion
JSON SCHEMAViewport
JSON SCHEMAPlusCode
JSON SCHEMAPoint
JSON SCHEMAPolyline
JSON SCHEMAQueryPrediction
JSON SCHEMARectangle
JSON SCHEMAReview
JSON SCHEMARoute
JSON SCHEMASearchNearbyRequest
JSON SCHEMASearchPlacesResponse
JSON SCHEMASearchTextRequest
JSON SCHEMAStep
JSON SCHEMAStructuredFormat
JSON SCHEMASuggestion
JSON SCHEMATextValuePair
JSON SCHEMATimeZoneTextValue
JSON SCHEMATransitDetails
JSON SCHEMATransitLine
JSON SCHEMATransitStop
JSON SCHEMAViewport
JSON SCHEMAScroll within the panel for all 99 ·
JSON Structure 52
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Google Maps Directions Bounds Structure
JSON STRUCTUREGoogle Maps Directions Directions Response Structure
JSON STRUCTUREGoogle Maps Directions Fare Structure
JSON STRUCTUREGoogle Maps Directions Geocoded Waypoint Structure
JSON STRUCTUREGoogle Maps Directions Lat Lng Structure
JSON STRUCTUREGoogle Maps Directions Leg Structure
JSON STRUCTUREGoogle Maps Directions Polyline Structure
JSON STRUCTUREGoogle Maps Directions Route Structure
JSON STRUCTUREGoogle Maps Directions Step Structure
JSON STRUCTUREGoogle Maps Directions Text Value Pair Structure
JSON STRUCTUREGoogle Maps Directions Time Zone Text Value Structure
JSON STRUCTUREGoogle Maps Directions Transit Details Structure
JSON STRUCTUREGoogle Maps Directions Transit Line Structure
JSON STRUCTUREGoogle Maps Directions Transit Stop Structure
JSON STRUCTUREGoogle Maps Geocoding Address Component Structure
JSON STRUCTUREGoogle Maps Geocoding Bounds Structure
JSON STRUCTUREGoogle Maps Geocoding Geocoding Response Structure
JSON STRUCTUREGoogle Maps Geocoding Geocoding Result Structure
JSON STRUCTUREGoogle Maps Geocoding Geometry Structure
JSON STRUCTUREGoogle Maps Geocoding Lat Lng Structure
JSON STRUCTUREGoogle Maps Geocoding Plus Code Structure
JSON STRUCTUREGoogle Maps Places Accessibility Options Structure
JSON STRUCTUREGoogle Maps Places Author Attribution Structure
JSON STRUCTUREGoogle Maps Places Autocomplete Request Structure
JSON STRUCTUREGoogle Maps Places Autocomplete Response Structure
JSON STRUCTUREGoogle Maps Places Circle Structure
JSON STRUCTUREGoogle Maps Places Formattable Text Structure
JSON STRUCTUREGoogle Maps Places Lat Lng Structure
JSON STRUCTUREGoogle Maps Places Localized Text Structure
JSON STRUCTUREGoogle Maps Places Location Bias Structure
JSON STRUCTUREGoogle Maps Places Location Restriction Structure
JSON STRUCTUREGoogle Maps Places Opening Hours Structure
JSON STRUCTUREGoogle Maps Places Parking Options Structure
JSON STRUCTUREGoogle Maps Places Payment Options Structure
JSON STRUCTUREGoogle Maps Places Period Structure
JSON STRUCTUREGoogle Maps Places Photo Media Structure
JSON STRUCTUREGoogle Maps Places Photo Structure
JSON STRUCTUREGoogle Maps Places Place Address Component Structure
JSON STRUCTUREGoogle Maps Places Place Prediction Structure
JSON STRUCTUREGoogle Maps Places Place Structure
JSON STRUCTUREGoogle Maps Places Plus Code Structure
JSON STRUCTUREGoogle Maps Places Point Structure
JSON STRUCTUREGoogle Maps Places Query Prediction Structure
JSON STRUCTUREGoogle Maps Places Rectangle Structure
JSON STRUCTUREGoogle Maps Places Review Structure
JSON STRUCTUREGoogle Maps Places Search Nearby Request Structure
JSON STRUCTUREGoogle Maps Places Search Places Response Structure
JSON STRUCTUREGoogle Maps Places Search Text Request Structure
JSON STRUCTUREGoogle Maps Places Structured Format Structure
JSON STRUCTUREGoogle Maps Places Suggestion Structure
JSON STRUCTUREGoogle Maps Places Viewport Structure
JSON STRUCTUREGoogle Maps Structure
JSON STRUCTUREScroll within the panel for all 52 ·
Examples 58
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Google Maps Geocode Example
EXAMPLEScroll within the panel for all 58 ·
Security Posture 4
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.
Google Maps Trust Center
SOC 2, SOC 3, ISO/IEC 27001:2022, ISO/IEC 27017:2015, ISO 22301:2019, ISO 9001:2015, ISO 50001:2018, NIST 800-53, FIPS 140-2, Cloud Security Alliance (CSA), TISAX, GDPR, EU Stan...
SECURITYAgentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Resources
Every other property we hold for Google Maps Platform — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 13
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 13 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/google-maps · machine-readable index on apis.io