TBM Bordeaux CLI

Every Bordeaux tram, bus, and ferry schedule offline in SQLite, plus real-time arrivals, ghost service detection, and journey planning no other Bordeaux transit tool offers.

Syncs the full TBM GTFS dataset locally so schedule lookups, stop searches, and frequency analysis work without an internet connection. Overlays live real-time data from the SIRI-Lite API for arrival predictions, vehicle tracking, and disruption alerts. Computes journeys, detects ghost services, and diffs timetable changes — capabilities no existing Bordeaux transit tool provides.

Created by @pawlclawbot (pawlclawbot).

Quick Start

# Health check — verifies API reachability and local store state
infotbm-pp-cli doctor --dry-run

# Download the full GTFS dataset into local SQLite
infotbm-pp-cli sync --full

# Find stops matching a name
infotbm-pp-cli stops --name Quinconces --json

# Real-time next arrivals at Quinconces
infotbm-pp-cli realtime stop --stop-id bordeaux:StopPoint:BP:3648:LOC --json

# Tram A headway patterns by hour
infotbm-pp-cli lines frequency --line A --json

Unique Features

These capabilities aren't available in any other tool for this API.

Schedule intelligence

• schedule diff — Surface trips that are scheduled in GTFS but absent from live real-time data — the buses that exist on paper but never showed up

  When an agent needs to know whether a scheduled service is actually running today, this is the only command that answers definitively

  infotbm-pp-cli schedule diff --stop BEQUI --line A --json
  

• lines stops — Print the ordered stop list for a line and direction, optionally with scheduled departure times

  When an agent needs the exact stop order for a tram line to plan boarding points or give directions, this is the canonical answer

  infotbm-pp-cli lines stops --line A --direction 0 --json
  

• schedule changes — Compare GTFS sync snapshots to detect added, removed, or modified routes on a line

  When an agent manages a commuter's routine, this proactively detects schedule changes that would break their timing

  infotbm-pp-cli schedule changes --line C --since 7d --json
  

• lines frequency — Compute average headways per hour from the SIRI estimated timetable

  When an agent evaluates transit reliability for scheduling, this shows the real-world gaps between departures by time of day

  infotbm-pp-cli lines frequency --line B --json
  

Journey intelligence

• trips last-departure — Find the latest departure from a stop that still reaches your destination before a cutoff time

  When an agent plans evening activities, this answers 'what is the absolute latest I can leave and still get home by transit'

  infotbm-pp-cli trips last-departure --from Victoire --to Pessac --before 23:30 --json
  

• trips reroute — When your current connection is delayed, compute the best alternate onward path using live vehicle data

  When an agent detects a delay notification, this computes the optimal recovery without re-planning from scratch

  infotbm-pp-cli trips reroute --at "Gare Saint-Jean" --to Meriadeck --delay 8 --json
  

• trips plan — Plan multi-modal journeys across tram, bus, and ferry using local GTFS data with live disruption awareness

  When an agent needs transit directions in Bordeaux without relying on third-party map APIs, this plans the route locally

  infotbm-pp-cli trips plan --from Victoire --to "Gare Saint-Jean" --depart 08:15 --json
  

Commute intelligence

• alerts impact — Filter all active disruptions to only those affecting your specific lines or stops

  When an agent monitors a commuter's daily lines, this filters noise to only relevant disruptions

  infotbm-pp-cli alerts impact --lines A,C,15 --json
  

Recipes

Morning commute check

infotbm-pp-cli realtime stop --stop-id bordeaux:StopPoint:BP:3648:LOC --json --select items.lineName,items.destinationName,items.expectedDepartureTime

Check next departures at your stop with only the fields that matter

Weekend disruption audit

infotbm-pp-cli alerts impact --lines A,B,C --json

Filter alerts to only tram lines before a weekend outing

Late night last train

infotbm-pp-cli trips last-departure --from Victoire --to Pessac --before 23:30 --json

Find the latest departure that still gets you home

Detect ghost services

infotbm-pp-cli schedule diff --stop BEQUI --line A --agent

Surface scheduled trams that are not showing up in real-time data

Weekly schedule change alert

infotbm-pp-cli schedule changes --line C --since 7d --json

Detect any trips added, removed, or shifted since last week's sync

Usage

Run infotbm-pp-cli --help for the full command reference and flag list.

Commands

agencies

• infotbm-pp-cli agencies - Transit agencies in the Bordeaux network

alerts

• infotbm-pp-cli alerts - Active service disruption alerts

fares

• infotbm-pp-cli fares - Fare structure including pricing and transfer rules

feed-info

• infotbm-pp-cli feed-info - GTFS feed metadata including validity dates and timestamps

kml

• infotbm-pp-cli kml - KML geographic data export with route geometry and stop locations

realtime

• infotbm-pp-cli realtime stop - Real-time departure information at a specific stop
• infotbm-pp-cli realtime vehicles - Real-time vehicle positions across the network

routes

• infotbm-pp-cli routes - All transit routes/lines in the TBM network

server-info

• infotbm-pp-cli server-info - API version and build information

siri

• infotbm-pp-cli siri check-status - SIRI service health check
• infotbm-pp-cli siri estimated-timetable - Estimated real-time timetable for a line
• infotbm-pp-cli siri general-message - General service messages and disruption information
• infotbm-pp-cli siri lines-discovery - Discover all lines with destinations and transport modes
• infotbm-pp-cli siri stop-monitoring - Real-time arrival/departure monitoring at a stop
• infotbm-pp-cli siri stoppoints-discovery - Discover all stop points with coordinates and serving lines

stops

• infotbm-pp-cli stops - All transit stops in the TBM network

Output Formats

# Human-readable table (default in terminal, JSON when piped)
infotbm-pp-cli agencies

# JSON for scripting and agents
infotbm-pp-cli agencies --json

# Filter to specific fields
infotbm-pp-cli agencies --json --select id,name,status

# Dry run — show the request without sending
infotbm-pp-cli agencies --dry-run

# Agent mode — JSON + compact + no prompts in one flag
infotbm-pp-cli agencies --agent

Agent Usage

This CLI is designed for AI agent consumption:

• Non-interactive - never prompts, every input is a flag
• Pipeable - --json output to stdout, errors to stderr
• Filterable - --select id,name returns only fields you need
• Previewable - --dry-run shows the request without sending
• Read-only by default - most commands only read data; import and sync write to the local store but do not mutate remote resources
• Offline-friendly - sync/search commands can use the local SQLite store when available
• Agent-safe by default - no colors or formatting unless --human-friendly is set

Exit codes: 0 success, 2 usage error, 3 not found, 4 auth error, 5 API error, 7 rate limited, 10 config error.

Health Check

infotbm-pp-cli doctor

Verifies configuration, credentials, and connectivity to the API.

Configuration

Config file: ~/.config/infotbm-pp-cli/config.json

Static request headers can be configured under headers; per-command header overrides take precedence.

Environment variables:

Name	Kind	Required	Description
INFOTBM_API_KEY	per_call	Yes	Set to your API credential.

agentcookie (optional)

If you use agentcookie to sync secrets across machines, this CLI auto-adopts agentcookie-managed credentials with no extra setup. When the daemon writes to this CLI's config, infotbm-pp-cli doctor reports agentcookie: detected and auth-status labels the source as agentcookie. Skip this section if you don't use agentcookie - the CLI works the same as any other.

Troubleshooting

Authentication errors (exit code 4)

• Run infotbm-pp-cli doctor to check credentials
• Verify the environment variable is set: echo $INFOTBM_API_KEY Not found errors (exit code 3)
• Check the resource ID is correct
• Run the relevant resource command (e.g., stops --name <name>, routes) to see available items

API-specific

• Empty arrivals response — Service may have ended for the day. Check with infotbm-pp-cli lines frequency --line <line> to see operating hours.
• Sync fails with timeout — The GTFS ZIP is ~15MB. Retry with infotbm-pp-cli sync --full --timeout 60s.
• Stop ID format confusion — Use stops --name <name> to find the full stop reference (e.g., bordeaux:StopPoint:BP:3648:LOC). Short codes like BEQUI also work for some endpoints.

Sources & Inspiration

This CLI was built by studying these projects and resources:

• JulienLavocat/InfoTBM-Client — JavaScript (5 stars)
• Almtesh/infotbm — Python (4 stars)
• drawbu/nextbus — Go (3 stars)

Generated by CLI Printing Press