MPPtempoquality 0.88

Search cities by keyword via Amadeus reference data — $0.005/request, pay with USDC on Tempo.

Price
$0.0054 / call
Protocol
mpp
Verified
no

What it does

This endpoint searches for cities by keyword using Amadeus reference data, returning matching city names and IATA codes. It is part of the StableTravel API suite, which provides pay-per-request access to flights, hotels, activities, transfers, real-time flight tracking (FlightAware), and Google Flights price comparison — all without API keys or subscriptions.

The `/api/reference/cities` endpoint accepts a required `keyword` query parameter (the city name to search) and optional parameters: `countryCode` (ISO 3166-1 filter), `max` (result limit), and `include=Airports` to embed associated airport data. It costs $0.0054 per call. Payment is handled automatically via the MPP protocol using USDC on the Tempo L2 chain (chainId 4217). The endpoint returns a JSON object with a `data` array of matching cities, optional `included` airport associations, and metadata.

StableTravel is operated by Merit Systems and serves as a unified gateway to Amadeus GDS, FlightAware AeroAPI, and Google Flights (via SerpAPI). The full API covers 70+ endpoints spanning flight search/booking, hotel discovery/booking, activity search, airport transfers, airline/airport reference lookups, real-time flight tracking, historical flight data, airport weather (METAR/TAF), and disruption statistics. Prices range from $0.001 to $0.40 per request depending on the endpoint. A complete OpenAPI 3.1 spec is published at `/openapi.json`.

Capabilities

city-searchiata-code-lookupkeyword-autocompleteairport-associationreference-dataamadeus-gdspay-per-requestmpp-protocoltempo-l2usdc-payment

Use cases

  • Resolve a city name to its IATA code before searching for flights or hotels
  • Build a city autocomplete/typeahead for a travel booking interface
  • Look up cities in a specific country for destination planning
  • Retrieve associated airports for a given city keyword
  • Agent-driven itinerary planning that needs to map user input to structured city codes

Fit

Best for

  • AI travel agents that need to resolve free-text city names to IATA codes
  • Autonomous booking workflows where city disambiguation is the first step
  • Lightweight reference lookups at sub-cent cost with no API key setup

Not for

  • High-volume batch geocoding (this is a keyword search, not a geocoder)
  • Applications that need full geographic coordinates — use the airports-by-geocode endpoint instead
  • Free-tier usage — every call costs $0.0054 via micropayment

Quick start

npx agentcash fetch "https://stabletravel.dev/api/reference/cities?keyword=Paris&include=Airports"

Example

Response

{
  "data": [
    {
      "name": "PARIS",
      "type": "location",
      "address": {
        "countryCode": "FR"
      },
      "subType": "CITY",
      "iataCode": "PAR"
    }
  ],
  "meta": {
    "count": 1
  },
  "included": {}
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with detailed parameter definitions, clear pricing ($0.0054/call), live 402 MPP challenge confirmed, and extensive guidance documentation. Response schema for this specific endpoint is generic (`items: {}`) so the example response is inferred from Amadeus conventions rather than directly captured.

Warnings

  • Response schema uses generic `items: {}` — actual response structure is inferred from Amadeus API conventions, not explicitly defined in the OpenAPI spec.
  • No example response is provided in the OpenAPI spec for this endpoint.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:31:29Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access