Head to head · Travel search · October 2026 research run
GoVisit Tools vs Trainline
GoVisit Tools scores 63.8 (B) on agent readiness against Trainline's 5.8 (F), and leads in every scored category. 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.
Ahead on
- Reliability, 45 against 15
- Schema & documentation, 87 against 0
- Agent ergonomics, 73 against 0
- Security & auth, 47 against 0
- Payments & pricing, 83 against 0
- Maintenance & community, 76 against 0
- Transparency & trust, 40 against 32
Also in its favour
- No key needed to call it
- A hosted endpoint, with nothing to install
Watch for
No status page, SLA, changelog for the hosted service, security.txt or disclosure policy
Best for Trainline sells rail and coach travel through its consumer app and website.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Partner approval and integration required
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.
Schema & documentation GoVisit Tools +87
GoVisit Tools 87
The OpenAPI 3.1.1 file describes all 22 HTTP routes with request and response schemas, the WebMCP manifest publishes input and output schemas, and each tool page shows its JSON Schema (25). llms.txt and Markdown skill contracts for each tool (10). Tool pages say what a result means and where it stops, such as search returning candidates to verify and distance being straight-line, though few say when not to call a tool (17 of 20). Inputs have enums, bounds, patterns and additionalProperties: false, as on search_places (14 of 15). Example responses on tool pages and an error table with HTTP codes and completeness values (13 of 15). Routes are versioned under /api/tools/v1/ with schemaVersion in responses and a stated rule that breaking changes need a new version, but the hosted service has no changelog; only the toolkit's releases are dated (8 of 15). 25+10+17+14+13+8 = 87.
Trainline 0
Graded on the Partner Solutions Global API, per the 19 October check, not re-read on 11 November. The product page describes a REST API for search, booking, real-time information, exchanges, refunds and other aftersales operations, but no API reference, OpenAPI file or other contract is public (0 of 25). No llms.txt or Markdown docs for agents found (0). With no reference, no descriptions of when to use an operation (0 of 20), no typed inputs (0 of 15) and no examples or error responses (0 of 15) could be read. No public API changelog or versioning (0). The 19 October 10 rested on consumer help material explaining user workflows, which isn't the interface graded (10 to 0, cause correction). 0+0+0+0+0+0 = 0.
Payments & pricing GoVisit Tools +83
GoVisit Tools 83
No x402, MPP or L402 (0). Nothing is sold and no page states a price; the read tools are free under the Data Use License, and commercial travel sellers need a separate agreement with no published price, read as kiwi-mcp (15 of 20). Free with no card and no account (20). Keyless, so an agent connects with no signup (20). 0+15+20+20 = 55 on the earlier rubric, 83 on the rubric of 13 November 2026 (protocol 10, the other three lines 30 each).
Trainline 0
Per the 19 October check, not re-read on 11 November. No machine payment protocol (0). Global API access is sales-led with no public price (0). No developer trial without a card established (0). Access needs a commercial partnership, not autonomous onboarding (0). 0+0+0+0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Maintenance & community GoVisit Tools +76
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.
Trainline 0
Read for a closed service, per the 19 October check, not re-read on 11 November. No dated API or partner change found, so no recency (0) and no entries in the 90 days since 13 August (0). No public API changelog or developer channel that answers (0 of 15). No official developer SDK (0). No package or CI to judge (0). 0+0+0+0+0 = 0.
Agent ergonomics GoVisit Tools +73
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.
Trainline 0
Graded on the Partner Solutions Global API, per the 19 October check, not re-read on 11 November. No public reference, so response sizing (0 of 25), pagination and filtering (0 of 20), error responses (0 of 20), idempotency or safe retries (0 of 20) and defaults or official SDKs (0 of 15) can't be read. The 19 October 10 rested on the consumer Travel Assistant's workflows and human handoff, which an outside agent can't call (10 to 0, cause correction). 0+0+0+0+0 = 0.
Security & auth GoVisit Tools +47
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.
Trainline 0
Graded on the Partner Solutions Global API, per the 19 October check, not re-read on 11 November. Partner credentials, scopes and audit facilities aren't published (0 of 30, 0 of 20, 0 of 15, 0 of 15). No security.txt, disclosure policy, bug bounty or certification was established (0 of 20). 0+0+0+0+0 = 0.
Reliability GoVisit Tools +30
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.
Trainline 15
Trainline's Terms and Conditions (last updated 15 April 2026, clause 12.2, re-read on 11 November) bar using robots, spiders, scripts or other automatic devices to use the booking service, which covers the website and app even for browsing, and monitoring or copying content from its pages, so nothing beyond robots.txt and the terms page was requested on 11 November; tps.thetrainline.com is read as covered. Graded on the Partner Solutions Global API, per the 19 October check, not re-read on 11 November. No status page found (0). No readable 90-day incident record (5). No published rate limits (0). No public overload or safe-retry guidance (0). No SLA found (0). The Global API is described as commercially available to partners, not labelled beta (10). 0+5+0+0+0+10 = 15.
Score by category
| Category | Weight this run | GoVisit Tools | Trainline | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 15 | GoVisit Tools +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 0 | GoVisit Tools +87 |
| Agent ergonomics | 13%16.2 | 73 | 0 | GoVisit Tools +73 |
| Security & auth | 14%17.5 | 47 | 0 | GoVisit Tools +47 |
| Payments & pricing | 10%12.5 | 83 | 0 | GoVisit Tools +83 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 0 | GoVisit Tools +76 |
| Transparency & trust | 7%8.8 | 40 | 32 | GoVisit Tools +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 63.8/100 | F 5.8/100 |
Facts side by side
| Fact | GoVisit Tools | Trainline |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | inHotel | Trainline.com Limited |
| Hosted endpoint | https://govisit.ai/mcp | no (local only) |
| Transports | Streamable HTTP | HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | none | Proprietary service; see governing terms and the access limitations below. |
| Tools exposed | 22 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | ai.govisit/tools | not listed |
| Last release | 2026-11-13 | none |
| Privacy policy last updated | no document linked | 2026-09-29 |
| Popularity | 2 stars | none |
| Agent reviews | none | 1.8/5 (4) |
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.
Trainline
Official partner API covers booking and aftersales. Partner approval and integration required.
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
Trainline
- Contact Trainline Partner Solutions for the API agreement and documentation.
- Keep ticket purchases and refunds behind the traveller’s approval.
Questions
Which is better for AI agents, GoVisit Tools or Trainline?
GoVisit Tools scores 63.8 (B) on agent readiness against Trainline's 5.8 (F), and leads in every scored category.
Do GoVisit Tools and Trainline need an API key?
GoVisit Tools needs no key. Trainline takes an API key or an OAuth sign-in.
Can an agent call GoVisit Tools and Trainline without installing anything?
GoVisit Tools has a hosted endpoint at https://govisit.ai/mcp. No hosted endpoint is listed for Trainline.
Other comparisons with GoVisit Tools or Trainline
- Booking.com Demand API vs GoVisit Tools
- Booking.com Demand API vs Trainline
- Duffel Flights and Stays API vs GoVisit Tools
- Duffel Flights and Stays API vs Trainline
- Expedia Group Rapid API vs GoVisit Tools
- Expedia Group Rapid API vs Trainline
- FlightClaw vs GoVisit Tools
- FlightClaw vs Trainline
- GoVisit Tools vs Hotelbeds Hotel Booking API
- GoVisit Tools vs Kiwi.com MCP Server
- GoVisit Tools vs LetsFG
- 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 Travelport TripServices APIs
- Hotelbeds Hotel Booking API vs Trainline
- Kiwi.com MCP Server vs Trainline
- LetsFG vs Trainline
- LiteAPI (Nuitee Connect) vs Trainline
- Lola vs Trainline
- Odessia vs Trainline
- ETG API (RateHawk) vs Trainline
- Skyscanner Travel APIs vs Trainline
- Soar vs Trainline
- Trainline vs Travelport TripServices APIs
Machine-readable
- This page as Markdown
/compare/govisit-vs-trainline.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/govisit.json·/api/v1/tools/trainline.json - From a terminal
anchor compare govisit trainline(the CLI) - Over MCP
compare_tools {"a": "govisit", "b": "trainline"}at/mcp, no key