Pricing
Pay for the traffic, not the features
Every tier gets every endpoint and the whole country. What changes is how hard you can hit it.
Enough to build something real and find out if it works.
- Every endpoint, no feature gates
- 30 requests a minute
- Nationwide stops, timetables and live positions
- Community support
For a product in front of real users.
- Everything in Free
- 300 requests a minute
- Email support, one working day
- Cancel any time
Card payment is being switched on.
For traffic that would rate-limit on Standard.
- Everything in Standard
- 1200 requests a minute
- Priority support
- Higher limits on request
Card payment is being switched on.
What counts as a request?
One call to one endpoint. Rate limits are per minute and per key, and every response tells you where you stand in the headers, so you find your ceiling before your users do.
What happens if I go over?
You get a 429 and the limit resets on the next minute. Nothing is billed by surprise and nothing is cut off — the free tier stays free whatever it does.
Is any data held back on the free tier?
No. Same endpoints, same national coverage, same live positions. The only difference between the tiers is throughput.
Where does the data come from?
Official sources: the Bus Open Data Service, the NaPTAN stop register and the national rail timetable — 387,881 stops and 1,445,967 journeys at the last refresh. Attribution requirements are in the docs.