Autocomplete hotel names via Amadeus for $0.005/request — no API keys, pay with USDC on Tempo.
What it does
The StableTravel hotel autocomplete endpoint returns matching hotel name suggestions from the Amadeus GDS database. It accepts a keyword string and a subType filter (HOTEL_LEISURE or HOTEL_GDS), with optional country code, language, and max-results parameters. The response is a JSON array of matching hotel entries. This endpoint is part of the broader StableTravel suite, which wraps Amadeus, FlightAware, and Google Flights data behind pay-per-request micropayments.
Pricing is $0.0054 per call (the OpenAPI spec lists the amount as 0.005400 USD). Payment is handled automatically via the MPP protocol using pathUSD on Tempo (chain 4217) or via x402. No API keys, OAuth tokens, or subscriptions are required — the micropayment itself serves as authentication. The endpoint is live and returns a 402 MPP challenge to unauthenticated callers, confirming it is operational.
The typical workflow for hotel booking starts with this autocomplete endpoint or the /api/hotels/list endpoint to discover hotel IDs, then proceeds to /api/hotels/search for offers, /api/hotels/offer for details, and /api/hotels/book to complete a reservation. The autocomplete endpoint is useful as a lightweight first step for agents building hotel search UIs or resolving user-typed hotel names to Amadeus identifiers.
Capabilities
Use cases
- —Resolve a user-typed hotel name to Amadeus hotel IDs before searching for offers
- —Build a hotel search autocomplete dropdown in a travel agent UI
- —Quickly validate whether a hotel exists in the Amadeus GDS database
- —Pre-filter hotels by country before running a full availability search
- —Let an autonomous agent disambiguate hotel names during trip planning
Fit
Best for
- —AI travel agents that need to resolve hotel names to bookable IDs
- —Applications building hotel search typeahead features
- —Workflows that chain autocomplete → search → offer → book via StableTravel
- —Developers who want Amadeus hotel data without managing API credentials
Not for
- —Searching hotel availability or pricing directly (use /api/hotels/search instead)
- —Non-hotel travel queries like flights or activities
- —Bulk hotel data extraction or scraping
Quick start
npx agentcash fetch "https://stabletravel.dev/api/hotels/autocomplete?keyword=Hilton&subType=HOTEL_GDS&max=5"Example
Response
{
"data": [
{
"id": 1,
"name": "HILTON PARIS OPERA",
"subType": "HOTEL_GDS",
"hotelIds": [
"HIPARCDO"
],
"iataCode": "PAR"
}
],
"meta": {
"count": 1
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with parameter definitions, clear pricing in x-payment-info, live 402 MPP challenge captured, extensive guidance documentation, and well-documented workflows. Slightly below 0.9 because no example response is provided in the spec (the example_response_json above is inferred from Amadeus conventions) and the response schema items are untyped ({}).
Warnings
- —Response schema items are untyped (empty objects) — actual response structure is inferred from Amadeus conventions, not explicitly documented in the OpenAPI spec.
Citations
- —Hotel autocomplete endpoint costs $0.005400 per request in USDhttps://stabletravel.dev/openapi.json
- —Endpoint uses MPP protocol with method tempo on chain 4217 (pathUSD)https://stabletravel.dev/openapi.json
- —Required parameters are keyword (string) and subType (HOTEL_LEISURE or HOTEL_GDS)https://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
- —Endpoint is live, returning 402 MPP challenge on HEAD requesthttps://stabletravel.dev/api/hotels/autocomplete