MPPtempoquality 0.88

Get seat maps for flights via Amadeus GDS — $0.03/request, pay with USDC on Tempo.

Price
$0.0324 / call
Protocol
mpp
Verified
no

What it does

The `/api/flights/seatmap` endpoint on StableTravel returns seat map data for flights. It supports both GET (by flight order ID) and POST (by passing flight offer objects directly). The underlying data comes from the Amadeus GDS. This endpoint is part of the broader StableTravel platform, 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 seatmap endpoint costs $0.03 per request. Payment is handled via the MPP protocol using USDC (pathUSD) on Tempo (chain ID 4217) or via x402. No authentication tokens or OAuth flows are required; the micropayment itself serves as authentication. The GET method requires a `flight-orderId` query parameter (the ID of a previously created flight order). The POST method accepts a JSON body with a `data` array of flight offer objects (obtained from a prior `/api/flights/search` call) and an optional `included.travelers` object.

The endpoint is live, confirmed by a 402 MPP challenge response. The full OpenAPI 3.1 schema is available at `https://stabletravel.dev/openapi.json`, documenting request parameters, request body schema, and response structure. Typical workflow: search flights → get seatmap (POST with offer) or book flight → get seatmap (GET with order ID).

Capabilities

flight-seatmapamadeus-gdspay-per-requestmicropayment-authget-and-postflight-offer-inputflight-order-inputusdc-paymenttempo-settlementx402-compatible

Use cases

  • Retrieve seat maps before booking to let travelers choose preferred seats
  • Display cabin layout and seat availability in a travel agent application
  • Augment flight offer comparison with seat comfort data (legroom, window/aisle)
  • Build autonomous travel booking agents that factor seat preferences into decisions
  • Post-booking seat map retrieval using a flight order ID

Fit

Best for

  • AI travel agents that need seat-level detail during flight booking workflows
  • Applications integrating Amadeus flight data without managing API keys
  • Developers wanting pay-per-call access to GDS seat maps with no subscription

Not for

  • Bulk seat inventory monitoring (per-call pricing adds up at scale)
  • Airlines needing real-time seat assignment/ticketing (this is read-only GDS data)

Quick start

# GET seatmap by flight order ID
npx agentcash fetch "https://stabletravel.dev/api/flights/seatmap?flight-orderId=ORDER_ID"

# POST seatmap with flight offer
npx agentcash fetch -X POST -H "Content-Type: application/json" \
  -d '{"data": [<flight-offer-object>]}' \
  "https://stabletravel.dev/api/flights/seatmap"

Example

Request

{
  "data": [
    {
      "id": "1",
      "type": "flight-offer",
      "source": "GDS",
      "itineraries": [
        {
          "segments": [
            {
              "number": "100",
              "arrival": {
                "at": "2025-06-15T11:30:00",
                "iataCode": "LAX"
              },
              "departure": {
                "at": "2025-06-15T08:00:00",
                "iataCode": "JFK"
              },
              "carrierCode": "AA"
            }
          ]
        }
      ]
    }
  ]
}

Response

{
  "data": [
    {
      "type": "seatmap",
      "decks": [
        {
          "seats": [
            {
              "cabin": "ECONOMY",
              "number": "12A",
              "travelerPricing": [
                {
                  "seatAvailabilityStatus": "AVAILABLE"
                }
              ],
              "characteristicsCodes": [
                "W"
              ]
            }
          ],
          "deckType": "MAIN"
        }
      ],
      "segmentId": "1",
      "flightOfferIds": [
        "1"
      ]
    }
  ]
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with request/response definitions, clear pricing ($0.03), live 402 MPP challenge confirmed, comprehensive guidance docs. Minor deduction: response schema for seatmap data items is loosely typed (empty `items: {}`), and no real example response was captured from a live call.

Warnings

  • Response schema for seatmap data array uses untyped items — actual response structure is inferred from Amadeus documentation patterns
  • Example request and response are illustrative based on Amadeus GDS conventions, not captured from a live call

Citations

Provenance

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

Agent access