Public Transportation
Transit discovery, departures, Journey, and freshness semantics.
Page actions
ROOTE exposes public-transport operations in the API. Transit Nearby and Departures are Data capabilities; Journey is a separate calculation capability.
| Operation | Scope | Status |
|---|---|---|
GET /v1/transit/nearby | data:read | Beta |
GET /v1/transit/stations/{id}/departures | data:read | Beta |
GET /v1/transit/journey | journey:read | Beta |
POST /v1/transit/journey | journey:read | Beta |
The two-scope assignments are active in production. Transit Nearby and Departures support anonymous Free access or authenticated data:read; Journey requires authenticated journey:read.
Departures and freshness
Departures can contain both scheduled and realtime observations:
scheduled_atis the timetable value;estimated_atis a realtime estimate when supplied;realtime: truemeans the observation includes realtime information;- a missing estimate is not the same as a zero delay.
Provider-backed objects can be fresh, stale, or of unknown freshness. A stale response is cached information retained as a fallback and must not be presented as live. Preserve timestamps, realtime, freshness status, provider provenance, and partial-coverage warnings.
Journey
GET and POST share the same journey:read authorization. GET covers direct A-to-B query parameters; POST supports ordered waypoints and structured constraints. Journey is not part of anonymous Free access and is not an MCP V1 tool.
Use the published OpenAPI contract for parameters and schemas.