Stop Building Data Pipelines. Start Building Mobility Products.

Collecting, validating, and maintaining global transit data is a full-time engineering problem. We've already solved it. One unified API for buses, trains, trams, and metro across 90+ countries - validated, real-time, and production-ready.

API Documentation
80,000+
Cities Covered
7,000+
GTFS Feeds
1,000+
Real-time GTFS-RT
99.5%
Uptime SLA

Plans & Pricing

Monthly Annual (Save up to 20%)

Pro

$20 /month

$240 Billed Annually

  • WikiRoutes crowdsourced data
  • Shared Mobility (GBFS) — 1,000+ operators
  • Pedestrian routing
  • Geocoding (forward & reverse)
  • Vector tiles
  • Priority email support

And, everything in Free

14-day free trial

Most popular

Business

$200 /month

$2,400 Billed Annually

  • Pedestrian routing
  • Geocoding (forward & reverse)
  • Vector tiles — 1,000,000/month
  • 100,000 requests/day
  • 2,000,000 requests/month
  • Project integration consulting

And, everything in Pro

14-day free trial

Enterprise

Custom
  • Unlimited requests
  • 99.5% SLA
  • Dedicated support (Slack, phone)
  • Regional server deployment
  • Custom rate limits
  • Volume-based pricing

And, everything in Business

Contact sales

Free

$0
  • BusMaps official GTFS data
  • Transit routes, stops, departures
  • Real-time vehicle positions
  • GTFS feed downloads
  • 10,000 requests/day
  • 150,000 requests/month
  • Email support
  • 5 RPS global rate limit
Validated & corrected data

Every GTFS feed passes automated error detection, coordinate validation, and schedule consistency checks before reaching the API.

See our data quality pipeline →
Used by
500+ developers
10M+ API calls/month
50+ countries

FAQ

How quickly can I get API access?

Sign in with your Google account — API keys are available immediately in your profile.

What is the difference between busmaps and WikiRoutes?

busmaps.com provides API access to 7,000+ official GTFS feeds from 10,000+ transit agencies. WikiRoutes.info adds crowdsourced coverage for 100+ countries. Both share the same API — switch between data sources with the capi-host header. Our projects

What coordinate system is used?

WGS84 (EPSG:4326), latitude/longitude format.

How are time zones handled?

ISO 8601 format. Provide times in UTC (with Z suffix) or local time.

What infrastructure is behind the API?

Dedicated servers with multi-layer caching and CDN distribution. Regional deployment available for enterprise clients.

Tell us about your project

Get integration guidance, priority support, or custom pricing. Optional — API access is instant without this form.