List hotels near any lat/lng coordinate via Amadeus GDS — $0.03 per request, no API key needed.
What it does
This endpoint returns a list of hotels near a given latitude/longitude pair. It is part of StableTravel, a pay-per-request travel API suite that wraps Amadeus GDS data for flights, hotels, activities, and transfers, plus FlightAware for real-time flight tracking. Payment is handled via the MPP (Micropayment Protocol) using USDC on Tempo (chain 4217) — no API keys, no OAuth, no subscriptions.
The `/api/hotels/list/by-geocode` endpoint accepts `latitude` and `longitude` as required query parameters, with optional filters for `radius`, `radiusUnit` (KM or MILE), `chainCodes`, `amenities`, `ratings` (star ratings 1–5), `hotelScore` (BEDBANK, DIRECTCHAIN, ALL), and `max` (default 100). It returns an array of Amadeus hotel objects with IDs that can be passed to `/api/hotels/search` to retrieve availability and pricing for specific dates. The typical hotel booking workflow is: list hotels → search offers by hotel IDs → confirm offer details → book.
Pricing is $0.032 per call (fixed, settled in pathUSD on Tempo L2). The endpoint is live and returns a 402 MPP challenge to unauthenticated callers. The full OpenAPI 3.1 schema is published at `stabletravel.dev/openapi.json` with complete parameter definitions and response schemas for all endpoints.
Capabilities
Use cases
- —Find hotels within a radius of a specific GPS coordinate for trip planning
- —Build a travel agent that discovers accommodation options near a user's destination
- —Power a map-based hotel search UI by querying hotels around a pin drop
- —Pre-filter hotels by star rating and chain before fetching availability and prices
- —Autonomous agent itinerary building: list hotels near an activity or airport
Fit
Best for
- —AI travel agents that need programmatic hotel discovery without API key management
- —Developers building location-based hotel search features
- —Autonomous agents that plan multi-step travel itineraries (list → search → book)
Not for
- —Direct hotel booking (use /api/hotels/book after getting offer IDs via /api/hotels/search)
- —Price comparison or availability checking (this endpoint returns hotel metadata, not offers)
- —Non-travel geocoding or general POI search
Quick start
npx agentcash fetch "https://stabletravel.dev/api/hotels/list/by-geocode?latitude=48.8566&longitude=2.3522&max=10"Example
Response
{
"data": [
{
"name": "EXAMPLE HOTEL PARIS",
"dupeId": 700000001,
"address": {
"countryCode": "FR"
},
"geoCode": {
"latitude": 48.8566,
"longitude": 2.3522
},
"hotelId": "HSPAR001",
"iataCode": "PAR",
"chainCode": "HS"
}
],
"meta": {
"count": 1,
"links": {
"self": "https://stabletravel.dev/api/hotels/list/by-geocode?latitude=48.8566&longitude=2.3522&max=10"
}
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed parameter definitions, clear pricing ($0.032/call), live 402 MPP challenge confirmed, and comprehensive guidance docs. Response schema items are untyped (empty `items: {}`), and no example response is provided in the spec, so the example response above is inferred from Amadeus conventions.
Warnings
- —Response schema data items are untyped in the OpenAPI spec (items: {}), so exact response shape is inferred from Amadeus documentation conventions.
- —No example response is provided in the OpenAPI spec for this endpoint.
Citations
- —Endpoint price is $0.032 per call (amount 0.032400 USD)https://stabletravel.dev/openapi.json
- —Required parameters are latitude and longitude; optional parameters include radius, radiusUnit, chainCodes, amenities, ratings, hotelScore, maxhttps://stabletravel.dev/openapi.json
- —Payment is via MPP with method tempo, intent charge, settled in pathUSD on chain 4217https://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Hotel booking workflow: list → search → offer → bookhttps://stabletravel.dev/openapi.json