Faretrotter Travel API

Name: Faretrotter Travel API
Brand: Faretrotter Travel API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationRouting DirectionsapiKey2 EndpointsREST

For Agents

Look up cities and points of interest and retrieve multimodal routes (flight, rail, bus, ferry, drive) between them.

Install Jentic One Beta

Connect the Faretrotter Travel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Faretrotter Travel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffaretrotter.com%2Ffaretrotter" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffaretrotter.com%2Ffaretrotter" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Faretrotter Travel API.

Resolve cities and points of interest to canonical place identifiers usable in route queries

Retrieve multimodal route options between two places, with mode, duration, and operator details

Compare ground transport options (rail, bus, ferry) against air routes for a single origin-destination pair

GET STARTED

Start building with Faretrotter Travel API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Faretrotter Travel API for, with concrete tasks.

★ Multimodal Itinerary Builder

Travel planning apps use Faretrotter to populate trip segments with all viable transport options between two cities. The /routes endpoint returns flights, trains, buses, ferries, and drive routes in a single call, so the planner does not need to integrate Skyscanner, Trainline, and bus aggregators separately. Integration takes a few hours given the spec only exposes two endpoints.

Resolve 'Paris' and 'Berlin' via /places, then call /routes to return the full list of transport options between them with mode and duration

Ground-Transport Fallback for Flight Search

Flight aggregators use Faretrotter to suggest rail or bus alternatives when a route has no available flights or fares exceed a threshold. The agent calls /routes for the same origin and destination and filters returned options by mode to surface ground alternatives. Adds resilience to itinerary search without a separate rail or bus integration.

When a flight search returns zero results between two cities, call /routes to fetch ground options and present rail and bus alternatives ranked by duration

Points of Interest Reachability

Travel guides and destination marketing sites use Faretrotter to show how reachable a point of interest is from major hub cities. The /places endpoint resolves the POI to an identifier, then /routes returns the modes and times from each candidate origin. Useful for SEO landing pages that answer 'how do I get to X from Y'.

Look up the Eiffel Tower in /places, then call /routes from a list of European hub cities and produce a reachability table

AI Travel Concierge via Jentic

Conversational travel agents use Jentic to call Faretrotter without managing API keys directly. The agent resolves a user's free-text origin and destination through /places, then queries /routes to return options that fit the user's constraints. Jentic isolates the apikey path-segment credential so the agent never sees the raw key, and the search-load-execute flow takes minutes instead of days.

Through Jentic, search 'find travel routes between cities', load the /routes operation, and return options for a user's requested origin-destination pair

Key Endpoints

2 endpoints — the faretrotter travel api returns multimodal transportation options between cities and points of interest, covering flights, trains, buses, ferries, and driving routes.

METHOD

PATH

DESCRIPTION

GET

/places

List or look up cities and points of interest

GET

/routes

Retrieve multimodal routes between two places

GET

/places

List or look up cities and points of interest

GET

/routes

Retrieve multimodal routes between two places

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Faretrotter Travel API by hand means learning that the API key is a segment inside the URL path rather than a header, and building each request against that base yourself. Through Jentic you install once, import Faretrotter from the API Directory, store the key once, and your agent calls it.

Permission scoping

Faretrotter exposes read-only route and place discovery, so limit the agent to the operations it needs, such as listing places or finding routes between them. You choose which of those two operations it may call, and both are lookups that make no changes to any account.

Credential isolation

Your Faretrotter API key is stored once, encrypted, by your own Jentic One instance and injected into the request path at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find travel routes between cities', and Jentic returns the /routes operation with its place-id input schema so the agent calls the right endpoint without browsing the Faretrotter docs.

FAQs

Specific to using Faretrotter Travel API through Jentic.

What authentication does the Faretrotter Travel API use?

Faretrotter uses an API key passed as a path segment in the base URL (https://api.faretrotter.com/v2.0/{apikey}). Through Jentic the key is stored encrypted in the vault and injected into the URL at execution time, so the key never enters the agent's prompt context.

Can I get multimodal routes with the Faretrotter Travel API?

Yes. The /routes endpoint returns flight, rail, bus, ferry, and drive options between two places in a single response. Resolve the origin and destination through /places first to get the identifiers /routes expects.

What are the rate limits for the Faretrotter Travel API?

Faretrotter does not publish explicit rate limits in the OpenAPI spec. Treat it as a metered travel data service, cache /places lookups since identifiers are stable, and back off on 429 responses if you hit them.

How do I look up routes between two cities through Jentic?

Install the SDK with pip install jentic, search for 'find travel routes between cities', load the /routes operation, and execute with the resolved origin and destination identifiers from /places. Get started with Jentic One, the self-hosted execution layer.

Does the Faretrotter Travel API include pricing or booking?

No. The spec exposes /places and /routes only - there is no fare quote or booking endpoint. Use Faretrotter for option discovery, then hand off to a booking provider such as Amadeus or Skyscanner for fares and reservations.

Can I limit what my agent is allowed to do with the Faretrotter Travel API?

Yes. Because you run Jentic One yourself, your own rules decide which Faretrotter operations the agent may call and which credentials it may use. The API exposes only two read-only lookups, resolving cities and points of interest via /places and retrieving multimodal routes via /routes, so you can allow just one of them or both. Both are discovery calls that make no changes to any account, and the agent can reach only what you have granted.