Provider coverage
Movmo wraps four flight providers behind a single normalized surface. The capability matrix below reflects the contractually-stable behavior of each adapter; runtime answers come from GET /v1/flights/providers/{provider}/capabilities.
| Provider | Type | Direct booking | Pricing step | Seat selection | Max passengers | Max connections |
|---|---|---|---|---|---|---|
| Amadeus | GDS | No | Yes | Yes | 9 | 3 |
| Duffel | API | Yes | No | Yes | 9 | 4 |
| Dohop | NDC | No | No | Yes | 9 | 4 |
| Darwin | PSS | Yes (with hold) | No | No | 9 | 3 |
Operational reality
Section titled “Operational reality”REST endpoints work across all four providers. The Model Context Protocol (MCP) search_flights and create_offer tools currently invoke Darwin only.
Partners using Amadeus, Duffel, or Dohop should drive their own search and submit the offer via REST POST /v1/flights/providers/{provider}/offers. Both paths then converge: the same offer ID flows through get_offer_details, update_passenger, create_booking, get_booking.
If broader MCP search coverage matters for your integration, raise it at onboarding.