> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dev.gojinko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# jinko ground-search

> Search live rail, coach and ferry inventory

Search live ground-transport connections, rail, coach and ferry, for a route and date. It handles requests like "train from London to Heathrow on 28 August" or "coach from Berlin to Prague next Friday for two adults and a child". Codes are ISO-country + city (GBLON for London), NOT IATA (LON); a wrong code returns no inventory rather than an error. Each result's `id` is a trip item token you can hand straight to the trip command to start a booking.

## Usage

```bash theme={null}
jinko ground-search [options]
```

## Options

| Flag                              | Required | Description                                                                                                                                                                                         | Default |
| --------------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `--departure-city <code>`         | No       | departure city code, ISO-country + city, e.g. GBLON for London. JSON: `departure_city`.                                                                                                             |         |
| `--arrival-city <code>`           | No       | arrival city code, ISO-country + city, e.g. FRPAR for Paris. JSON: `arrival_city`.                                                                                                                  |         |
| `--departure-stations <codes...>` | No       | specific departure station codes, e.g. GBLONLPB. More specific than --departure-city, and wins when both are given. JSON: `departure_stations`.                                                     |         |
| `--arrival-stations <codes...>`   | No       | specific arrival station codes. Wins over --arrival-city. JSON: `arrival_stations`.                                                                                                                 |         |
| `--date <date>`                   | Yes      | departure date (YYYY-MM-DD). JSON: `departure_date`.                                                                                                                                                |         |
| `--return-date <date>`            | No       | return date (YYYY-MM-DD), makes it a round trip. JSON: `return_date`.                                                                                                                               |         |
| `--adults <n>`                    | No       | number of adults (default 1). JSON: `passengers[].pax`.                                                                                                                                             | `"1"`   |
| `--children <ages...>`            | No       | children ages, e.g. 8 12, each becomes its own passenger group. JSON: `passengers[].max_age`.                                                                                                       |         |
| `--carriers <codes...>`           | No       | restrict to specific carrier codes, e.g. HEXR. JSON: `carrier_codes`.                                                                                                                               |         |
| `--currency <code>`               | No       | ISO 4217 currency code, e.g. GBP. JSON: `currency`. NOTE: currently REQUIRED in practice, the provider rejects a search without one, and the schema marking it optional is a known server-side bug. |         |
| `--locale <locale>`               | No       | response locale, e.g. en. JSON: `locale`.                                                                                                                                                           |         |
| `--user-intent <text>`            | No       | the end user's request in their own words, forwarded to Jinko for observability and relevance (avoid PII). Env fallback: JINKO\_USER\_INTENT. JSON: `intent.user_intent`.                           |         |