LetsFG vs LiteAPI (Nuitee Connect)

LetsFG

Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients. Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions.

LiteAPI (Nuitee Connect)

Sandbox key at sign-up, same base URL as production, no card. Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools.

LetsFG

1. Start on /v1/sandbox/ with no key; the booking states, questions and timings match production
2. After book_flight, poll get_flight_booking every 20 to 30 seconds and answer questions before expires_at_ms; an unanswered price change fails the booking and releases the hold
3. Honour retry_after_seconds on a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and early retries lengthen the pause
4. Fetch results with get_flight_results and the search_id rather than searching again, which spends allowance
5. Send the same idempotency_key when retrying a booking after a timeout
6. Treat a 410 as a retired route and read the replacement path in its body

LiteAPI (Nuitee Connect)

1. Use /hotels/rates with a short hotelIds list from /data/hotels; a broad rates call is slow and large
2. Always prebook before book and read the cancellation policy in the prebook response, since refundability differs per rate
3. Send a unique clientReference on book; a repeat returns error 4005 instead of a second booking
4. Set margin explicitly on every rates call. Zero means net rates with no commission to you
5. Send the key to the MCP in an X-Api-Key header rather than ?apiKey= where the client allows it