Query the Transit.land REST API for feed registry and transit entity data

domain: transit.land · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Register for an API key and authenticate via the apikey query parameter or header
  2. Query the v2 REST API base for feeds, feed_versions, operators, routes, stops, or trips
  3. Use the /feeds endpoint to discover feed URLs cataloged in the community-maintained Transitland Atlas registry
  4. Request geojson, geojsonl, or png response formats where geographic entities support it, for map rendering
  5. Use feed_versions to pin analysis to a specific historical import of an agency's GTFS rather than always the latest

Known gotchas

Related routes

Use the Transitland v2 GraphQL API to run custom multi-entity transit data queries
transit.land · 5 steps · unrated
Query the Transitland v2 REST API for aggregated multi-agency GTFS stop, route, and schedule data
transit.land · 5 steps · unrated
Pull fleet telematics data from the Geotab API using Get and GetFeed calls
geotab.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans