Amazon Location Service
Amazon Location Service provides location-based services including maps, places, routes, trackers, and geofences, enabling developers to add location functionality to applications securely and cost-effectively.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon Location Service the way a machine reads it — 45 machine-readable artifacts across 1 API, 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 — Amazon Location Service scores 70.3/100 (exemplar), with a separate agent-readiness read of 48/100 (agent ready). 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 Amazon Location Service
Each block below is one kind of artifact we hold for Amazon Location Service. 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 1
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.
Amazon Location Service Maps API
Map resource management
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Amazon Location Service API
POSTMANOpen Collections 1
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).
Amazon Location Service API
OPEN COLLECTIONArazzo Workflows 9
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.
Amazon Location Service Find or Create Map
Reuse an existing map by name if present, otherwise create it.
ARAZZOAmazon Location Service Find or Create Tracker and Report Position
Reuse a tracker if it exists, else create it, then push a position.
ARAZZOAmazon Location Service Fleet Onboarding
Provision a map and a tracker, then report a first device position.
ARAZZOAmazon Location Service Geocode Address and Provision Map
Geocode free-form text and stand up a map to render the result.
ARAZZOAmazon Location Service Geocode Address into Tracker Position
Geocode text to coordinates and record them as a device position.
ARAZZOAmazon Location Service Map Inventory Audit
List all map resources and pull full detail on the first entry.
ARAZZOAmazon Location Service Map Lifecycle Teardown
Create, inspect, and delete a map resource in a single guarded flow.
ARAZZOAmazon Location Service Provision and Verify Map
Create a map resource and confirm it is queryable before use.
ARAZZOAmazon Location Service Provision Tracker and Update Position
Create a tracker then push an initial device position update to it.
ARAZZOScroll within the panel for all 9 ·
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.
Amazon Location Service 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.
Features 6
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.
Maps
Render interactive maps with customizable styles using vector tiles and raster tiles.
Places Search
Search for addresses, points of interest, and geographic coordinates.
Route Calculation
Calculate optimal routes with turn-by-turn directions and estimated travel time.
Geofencing
Create virtual boundaries and detect when tracked devices enter or exit those areas.
Asset Tracking
Track the real-time position of assets, vehicles, and people.
Data Privacy
Data does not leave AWS infrastructure, keeping location data private and secure.
Semantic Vocabularies 1
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.
Spectral 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.
Amazon Location Service API Rules
SPECTRALAmazon Location Service API Rules
SPECTRALJSON Schema 3
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.
JSON Structure 2
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.
Amazon Location Service Map Structure
JSON STRUCTUREAmazon Location Service Tracker Structure
JSON STRUCTUREExamples 2
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.
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.
Agentic 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 4
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.
Fleet Management
Track vehicle fleets in real time and optimize routes for delivery efficiency.
Store Locator
Build store locators and proximity-based search for retail applications.
Geofence Alerts
Send notifications when assets enter or exit defined geographic boundaries.
Map Visualization
Embed interactive maps in web and mobile applications.
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.
Amazon Cognito
Authenticate map and location requests using Cognito identity pools.
AWS IoT Core
Ingest device location data from IoT Core into Location Service tracking.
Amazon EventBridge
Trigger events when geofences are entered or exited via EventBridge.
HERE Technologies
Use HERE maps and location data as a data provider within Location Service.
Esri
Access Esri basemaps and location data through Amazon Location Service.
Resources
Every other property we hold for Amazon Location Service — 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 5
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-location-service · machine-readable index on apis.io