Amadeus Location Score
Browse all Amadeus APIsOfficial vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchoauth21 EndpointsREST
For Agents
Score the area around a coordinate by travel categories - sights, restaurants, nightlife, transport - to recommend neighbourhoods or compare candidate stay locations.
Use for: Score the area around these coordinates for sightseeing and dining, Find the best neighbourhood for nightlife within 2km of this hotel, Compare two candidate stay locations by their surrounding amenity scores, Get category-rated areas for a city centre coordinate
Not supported: Does not return individual place names, hotels, or routing - use for category-level area scoring only.
The Amadeus Location Score API returns category-rated areas around a geographic point, scoring nearby zones for travel-relevant categories such as sights, restaurants, shopping, nightlife, and transport. It is designed for travel planners that need to characterise a destination beyond a single coordinate - surfacing 'where to stay for nightlife' or 'best zone for sightseeing' in a city. The single endpoint accepts latitude and longitude with optional radius and category filters and returns rated polygons with a score per category.
Install Jentic One Beta
Connect the Location Score to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Location Score, 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%2Famadeus.com%2Famadeus-location-score" | 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%2Famadeus.com%2Famadeus-location-score" | 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 Location Score API.
Score the area around a coordinate by travel category - sights, restaurants, shopping, transport, nightlife
Compare candidate hotel coordinates by their surrounding area scores before recommending one
Filter rated areas by a specific category to find the best zone for that activity
Adjust the search radius to match user preferences from immediate-neighbourhood to multi-kilometre
Return rated polygons that can be rendered as a heatmap on a city map
Use Cases
Patterns agents use Location Score API for, with concrete tasks.
★ Neighbourhood recommendation engine
Help travellers choose where in a city to stay by ranking neighbourhoods on the categories that matter to them. The Location Score API returns scored areas around a city-centre coordinate with sub-scores for sights, restaurants, shopping, transport, and nightlife, so a recommender can match traveller preferences to zones rather than just to hotels. Useful for first-time visitors who do not know a destination's geography.
Call GET /location/analytics/category-rated-areas with latitude=48.8566 longitude=2.3522 radius=2 and return the highest-scoring zone for the 'restaurants' category.
Hotel-location qualifier
Enrich hotel search results by scoring the area around each candidate hotel's coordinates. A hotel's location is often the determining factor in a booking decision; Location Score quantifies it by category so the UI can surface 'great for sightseeing' or 'good transport links' badges next to each hotel. Combine with Hotel Search and Hotel Ratings for a richer ranking signal.
For each hotel in a Hotel Search result set, call Location Score with the hotel's geocode and attach its 'sights' and 'transport' scores to the response.
AI travel planner zone selection
An AI agent planning a multi-day trip uses Location Score to pick a base neighbourhood that fits the user's stated interests - for example, prioritising 'sights' for a sightseeing-heavy trip and 'restaurants' for a food-focused one. The agent calls Jentic to discover Location Score, executes it for several candidate coordinates, and recommends the highest-scoring zone with a citation of the category sub-scores.
Use Jentic to search 'score a destination area', execute Location Score for three candidate coordinates, and return the one with the highest combined score for the user's chosen categories.
Key Endpoints
1 endpoints — the amadeus location score api returns category-rated areas around a geographic point, scoring nearby zones for travel-relevant categories such as sights, restaurants, shopping, nightlife, and transport.
METHOD
PATH
DESCRIPTION
GET
/location/analytics/category-rated-areas
Get category-rated areas around a coordinate
GET
/location/analytics/category-rated-areas
Get category-rated areas around a coordinate
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Location Score by hand means running the Amadeus Self-Service OAuth 2.0 client_credentials exchange, refreshing the bearer token before it expires, choosing the test or production host, and mapping latitude, longitude, radius, and category query parameters, then parsing the rated polygons out of the response. Through Jentic you install once, import Location Score from the API Directory, store the client_id and client_secret once, and your agent calls it.
Permission scoping
The coordinate, radius, and category filters travel as query parameters on the GET to /location/analytics/category-rated-areas, not in the URL path, so scoping is by operation rather than by a specific location. Limit the agent to the operations it needs, such as scoring an area by category, and it stays a read-only analytics caller with no path to hotel or booking operations.
Credential isolation
Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the client_credentials exchange and injects a fresh bearer token at execution time. The secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'score a destination area', and Jentic returns the /location/analytics/category-rated-areas operation with its latitude, longitude, radius, and category parameters so the agent calls it directly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Location Score API through Jentic.
What authentication does the Location Score API use?
OAuth 2.0 client credentials. Exchange your Amadeus API key and secret for a bearer access token via the authorization endpoint, then send it on each call. Through Jentic, your client secret stays encrypted in the vault and only a scoped token is exposed to the agent.
What categories does the API score an area on?
Each rated area returns a sub-score per travel category - typical categories include sights, restaurants, shopping, nightlife, and transport. Filter by a single category via the categories query parameter to retrieve only the ones relevant to your use case.
What inputs does the endpoint require?
GET /location/analytics/category-rated-areas requires latitude and longitude. You can optionally pass radius (in kilometres) and a categories filter. The response is a set of polygons with category scores you can render on a map or rank in a recommender.
What are the rate limits for the Location Score API?
Amadeus enforces per-second and per-month transaction quotas that vary by environment. The test environment (test.api.amadeus.com/v1) is suitable for development with low limits; production tiers are set in your Amadeus for Developers contract.
How do I score a destination area through Jentic?
Install with pip install jentic, then search 'score a destination area' to find the Location Score operation. Load its schema and execute with latitude and longitude. Jentic returns the parsed category scores ready to feed into a recommender. Get started with Jentic One, the self-hosted execution layer.
Is full coverage available in the test environment?
No - the test environment returns scores for only a few selected cities. For full coverage you must upgrade to production via the Amadeus for Developers self-service portal.
Can I limit what my agent is allowed to do with the Amadeus Location Score API?
Yes. Because Jentic One is self-hosted, you run it and your own rules decide which operations and credentials the agent may use. Location Score exposes a single read-only operation, GET /location/analytics/category-rated-areas, so you can grant the agent that one call and nothing else, keeping it a category-scoring analytics caller with no path to hotel or booking operations. The coordinate, radius, and category filters travel as query parameters rather than in the URL path, so you scope access by operation, and your Amadeus client credentials stay under your control and are never placed in the agent's prompt.
GET STARTED