Head to head · Travel search · October 2026 research run
GoVisit Tools vs LetsFG
LetsFG scores 66.5 (B) on agent readiness against GoVisit Tools's 63.8 (B), and leads in 6 of 7 scored categories. Both do travel search.
Best travel search and booking APIs for AI agents · All 120 travel comparisons
Which one, for what
Best for Travel discovery for a trip planner: find destinations and places, read published profiles, visit facts and FAQs.
Also in its favour
- No key needed to call it
- No incidents deducted, where LetsFG loses 7 points for them
Watch for
No status page, SLA, changelog for the hosted service, security.txt or disclosure policy
LetsFG B
Best for A personal agent that wants to search widely and book with the traveller's own card, starting in a free sandbox.
Ahead on
- Reliability, 55 against 45
- Agent ergonomics, 83 against 73
- Security & auth, 66 against 47
- Maintenance & community, 88 against 76
- Transparency & trust, 65 against 40
Also in its favour
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Transparency & trust LetsFG +25
GoVisit Tools 40
The editorial half. A closed service whose Data Use License names the licensor, its registered office and Swiss law, and sets out permitted use, attribution, caching and AI-training limits. The toolkit is MIT (16 of 30). govisit.ai has no privacy policy. inHotel's policy of 13 February 2024 gives an 18-month default retention for its chat service but doesn't mention GoVisit, MCP or HTTP tool calls; the licence asks callers to cache for 24 hours at most (8 of 30). A stated rule that breaking changes get a new endpoint version and a migration, with no notice period or dated notices (8 of 20). inHotel's policy names Webflow, Wized, Memberstack, AWS, Google Cloud and Stripe for its own service, with no data locations, and nothing for GoVisit (6 of 20). 16+8+8+6 = 38. The provenance half is computed from the provenance block.
LetsFG 65
SDKs, CLI and stdio MCP are MIT. Since June 2026 they're clients of the closed cloud API, which runs under terms (last updated 31 October 2026) naming Mental Balance Sp. z o.o. under Polish law (20 of 30). The privacy policy, also last updated 31 October, names the controller and gives retention per data type (anonymous search sessions up to 24 months, bookings normally up to 3 years after the trip, payment and accounting records 5 years, account data up to 12 months after closure). No DPA found (25 of 30). Retirements carry dates and the old routes answer 410 naming the replacement, but we found no advance notice period (8 of 20). Processors named (Revolut, Stripe, Google Cloud, Hetzner, Cloudflare, Google Analytics) with SCCs for transfers. The AI providers are described as processors that don't train on the data but aren't named (15 of 20). 20 + 25 + 8 + 15 = 68.
Security & auth LetsFG +19
GoVisit Tools 47
No credentials, so there is no secret to leak and nothing to scope or revoke, read as kiwi-mcp (20 of 30). Every tool reads published pages and none writes, books or spends (20). Results are profile text written by the businesses listed and their agents. The docs tell callers to treat search matches as candidates, follow source links and keep provenance and warnings, but give no prompt-injection guidance (7 of 15). No audit log or per-call view; there is no account (0). security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0). 20+20+7+0+0 = 47.
LetsFG 66
Hosted MCP uses OAuth 2.1 with PKCE (S256), dynamic client registration, five scopes split by search and book for flights and hotels, one-hour access tokens and rotating refresh tokens that revoke the grant on reuse. The Developer API uses an X-API-Key header, and we found no key-in-URL option (30). Search and book scopes are separate, the card is held rather than charged until a PNR exists, price changes come back as questions the traveller answers, and changing the card goes through an emailed link (16 of 20). Results come from airline and booking-site pages that LetsFG reads, and we found no injection guidance (5 of 15). get_agent_profile shows usage and bookings have status histories; no per-call log for the operator (7 of 15). SECURITY.md with security@letsfg.co and a 48-hour acknowledgement target, CI actions pinned to SHAs, no security.txt (404 again on 2 November), bug bounty or certification (8 of 20). 30 + 16 + 5 + 7 + 8 = 66.
Maintenance & community LetsFG +12
GoVisit Tools 76
Read as a closed service, with the toolkit for releases. The newest change is toolkit 0.2.1 on 13 November 2026, with docs pages updated 7 November and the licence on 8 November (30). Three toolkit tags in the window, v0.1.0 and v0.2.0 on 1 November and v0.2.1 on 13 November (20). No public changelog for the hosted service. The Reliability page sends support to an issue on GitHub inhotel-io/govisit-content, which answered 404 on 15 November; info@inhotel.io is listed on inhotel.io (3 of 15). Four entries under the verified namespace ai.govisit in the official MCP registry (15). The toolkit's Verify toolkit workflow passed on its last three runs on main, with two pinned dev dependencies and no install scripts (8 of 10). 30+20+3+15+8 = 76.
LetsFG 88
Last release letsfg 2026.5.105 on PyPI, tagged 17 October 2026 with a CLI change for declined cards, by the repository's tags; commits to 25 October (30). In the 90 days from 4 August, tags v2026.5.88 (4 August), v2026.5.101 (14 September), v2026.5.102 and v2026.5.103 (2 October), and v2026.5.105 (17 October), with letsfg-mcp 2026.5.77 and 2026.5.78 on npm in the same release commits (20). Outside pull requests merged on 2 October (#220, a Bearer-lane round-trip fix) and 21 October (#234), and fixes on 2 October cite #221 and #223. Open issue counts and reply times unread, as GitHub's pages answer 403 in our session (15 of 25). In the official MCP registry as io.github.LetsFG/letsfg, a GitHub-verified namespace, latest 2026.5.77 (14 September) while server.json in the repository says 2026.5.79 (15). CI on push and pull request for both TypeScript packages and the Python SDK, Actions pinned to SHAs, Dependabot for actions. We didn't confirm the branch is green (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.
Reliability LetsFG +10
GoVisit Tools 45
Read with the hosted lines. No status page found (0) and so no incident history to read (5). Limits are published with numbers, 30 valid requests a minute per IP shared by HTTP and MCP, 4 KiB request bodies and 4 MiB page reads (15). The Reliability page documents a 429 with Retry-After (currently 60 seconds) and bounded backoff on 503, and every tool only reads (15). It states there is no service-level availability commitment and no latency SLA (0). No beta or preview label on the MCP server, which reports version 1.0.0, or the HTTP API (10). 0+5+15+15+0+10 = 45.
LetsFG 55
A connector health dashboard at letsfg.co/developers/connectors/health with 1-hour to 7-day windows. Re-read on 2 November, it still renders client-side from the site's own /api/ path (which robots.txt closes), shows connectors rather than the API, and has no incident log (10 of 20). No readable incident history (5). Limits published with numbers, hosted MCP search at 10 per 10 minutes, 30 an hour and 100 a day per account (and per card once one is added), Developer API limit 1 to 200 (15). Over-limit answers 429 with retry_after_seconds and pauses of 10 minutes up to 24 hours, and booking takes an idempotency_key with documented retry behaviour (15). No SLA (0). The API, MCP and sandbox aren't labelled beta (10). 10 + 5 + 15 + 15 + 0 + 10 = 55.
Agent ergonomics LetsFG +10
GoVisit Tools 73
22 tools, in the 11 to 30 band. The Agent Skill packs (Travel Planner 18, Destination 13, Local Business 10) are subsets for skills, not MCP toolsets (15). Results capped at 20 items with limit, filters by country, destination and radius around a place or coordinates, and section reads for one part of a page. No cursor for a next page was found (14 of 20). Documented HTTP codes plus completeness values (invalid-input, not-found, unavailable) and warnings in the envelope (16 of 20). Every tool carries readOnlyHint in tools/list and only reads, so retries are safe (20). search_places needs only query, with defaults for mode and limit. No official SDK; the docs use the MCP TypeScript SDK and the toolkit ships skills and plugins (8 of 15). 15+14+16+20+8 = 73.
LetsFG 83
The hosted MCP lists 24 tools, two of them hidden from the model as app-only, and present_flight_options cuts results to three picks (18 of 25). Result limits, cabin, time-window and stopover filters, refundable-only and airline-only flight filters (documented 25 October), and a search_id to page results without re-searching (18 of 20). Error codes an agent can act on, such as 402 search_allowance_exhausted versus payment_method_required, and missing_details with missing_fields (20). Idempotency keys on booking with retry guidance; no readOnlyHint or destructiveHint annotations in the stdio server source, re-read on 2 November (12 of 20). Three required search inputs, Python and JavaScript SDKs (15). 18 + 18 + 20 + 12 + 15 = 83.
Score by category
| Category | Weight this run | GoVisit Tools | LetsFG | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 55 | LetsFG +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 83 | GoVisit Tools +4 |
| Agent ergonomics | 13%16.2 | 73 | 83 | LetsFG +10 |
| Security & auth | 14%17.5 | 47 | 66 | LetsFG +19 |
| Payments & pricing | 10%12.5 | 83 | 85 | LetsFG +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 88 | LetsFG +12 |
| Transparency & trust | 7%8.8 | 40 | 65 | LetsFG +25 |
| Negative events | ≤15 | 0 | -7 | |
| Total | B 63.8/100 | B 66.5/100 |
Facts side by side
| Fact | GoVisit Tools | LetsFG |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | inHotel | LetsFG |
| Hosted endpoint | https://govisit.ai/mcp | https://letsfg.co/developers/api/v1 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Price for travel search | free | $0.005 per call |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 22 | 24 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | ai.govisit/tools | io.github.LetsFG/letsfg |
| Last release | 2026-11-13 | 2026-10-17 |
| Terms last updated | not read yet | 2026-09-19 |
| Privacy policy last updated | no document linked | 2026-09-19 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 2 stars | 2.1k stars, 157 npm/wk, 260 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |
How the scores have moved
GoVisit Tools
No score change since it was listed.
Verdicts
GoVisit Tools
Agents get 22 keyless, read-only MCP and HTTP tools for GoVisit's published destinations and places, with typed schemas, an OpenAPI file and documented limits and errors. Coverage is what businesses publish on govisit.ai, with no booking, prices or availability, no status page or privacy policy, and a licence that forbids benchmarking with the data.
LetsFG
Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients and a keyless sandbox. Tickets are bought by a LetsFG booking agent after the hold, and the stdio tool descriptions still call search unlimited and booking free of LetsFG charges, against the docs' caps and the terms' service fee.
Before you call either
GoVisit Tools
- Treat
search_placesresults as candidates and read the place profile before stating facts; the score is a ranking signal - Pass
pagePathas the pathname of a returned GoVisit URL with its language prefix, such as/en/places - On 429 wait for Retry-After (60 seconds) and keep to 30 calls a minute across all tools
- Get prices, availability and bookings from another source; opening hours are published values, not live
- Keep GoVisit attribution and cache results for 24 hours at most, per the Data Use License
LetsFG
- Start on
/v1/sandbox/with no key; the booking states, questions and timings match production - After
book_flight, pollget_flight_bookingevery 20 to 30 seconds and answer questions beforeexpires_at_ms; an unanswered price change fails the booking and releases the hold - Honour
retry_after_secondson a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and repeat overruns lengthen the pause up to 24 hours - Fetch results with
get_flight_resultsand thesearch_idrather than searching again, which spends allowance - Send the same
idempotency_keywhen retrying a booking after a timeout - Treat a 410 as a retired route and read the replacement path in its body
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Test a flight search with LetsFG sandbox, for LetsFG
Questions
Which is better for AI agents, GoVisit Tools or LetsFG?
LetsFG scores 66.5 (B) on agent readiness against GoVisit Tools's 63.8 (B), and leads in 6 of 7 scored categories.
Which is cheaper for travel search, GoVisit Tools or LetsFG?
GoVisit Tools, at free against $0.005 per call for LetsFG. These are the vendors' published prices for the job.
Do GoVisit Tools and LetsFG need an API key?
GoVisit Tools needs no key. LetsFG takes an API key or an OAuth sign-in.
Can an agent call GoVisit Tools and LetsFG without installing anything?
Yes. GoVisit Tools has a hosted endpoint at https://govisit.ai/mcp and LetsFG at https://letsfg.co/developers/api/v1.
Are GoVisit Tools and LetsFG open source?
No open-source release is listed for GoVisit Tools. LetsFG is open source (MIT).
Other comparisons with GoVisit Tools or LetsFG
- Booking.com Demand API vs GoVisit Tools
- Duffel Flights and Stays API vs GoVisit Tools
- Expedia Group Rapid API vs GoVisit Tools
- FlightClaw vs GoVisit Tools
- GoVisit Tools vs Hotelbeds Hotel Booking API
- GoVisit Tools vs Kiwi.com MCP Server
- GoVisit Tools vs LiteAPI (Nuitee Connect)
- GoVisit Tools vs Lola
- GoVisit Tools vs Odessia
- GoVisit Tools vs ETG API (RateHawk)
- GoVisit Tools vs Skyscanner Travel APIs
- GoVisit Tools vs Soar
- GoVisit Tools vs Trainline
- GoVisit Tools vs Travelport TripServices APIs
- LetsFG vs Lola
- LetsFG vs Trainline
- Booking.com Demand API vs LetsFG
- Expedia Group Rapid API vs LetsFG
- Hotelbeds Hotel Booking API vs LetsFG
- LetsFG vs ETG API (RateHawk)
- Duffel Flights and Stays API vs LetsFG
- FlightClaw vs LetsFG
- Kiwi.com MCP Server vs LetsFG
- LetsFG vs LiteAPI (Nuitee Connect)
- LetsFG vs Odessia
- LetsFG vs Skyscanner Travel APIs
- LetsFG vs Soar
- LetsFG vs Travelport TripServices APIs
Machine-readable
- This page as Markdown
/compare/govisit-vs-letsfg.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/govisit.json·/api/v1/tools/letsfg.json - From a terminal
anchor compare govisit letsfg(the CLI) - Over MCP
compare_tools {"a": "govisit", "b": "letsfg"}at/mcp, no key