Contents
Documentation
Plans, quotas, and billing
Last updated
This page explains the terms behind the plans on Plans and pricing. For prices and what each plan includes, see that page.
Monthly quotas
Every plan has a monthly quota for each API it includes.
- A request past a quota is refused until the quota resets the next month.
- On Explorer and Hobbyist/Academic, quotas are fixed.
- On Pay As You Go, each API starts with a quota of 1,000,000 requests a month. The quota protects you from runaway bills, for example a client stuck in a retry loop. For higher volumes and discounted rates, ask about Enterprise pricing.
What counts against each quota
| Usage | Counts against |
|---|---|
| REST API requests | REST API quota |
| GTFS Realtime feed downloads | REST API quota |
| Static GTFS feed downloads, current and historical | The plan's download quotas, not the REST API quota |
| Routing Platform requests, transit and street | Routing quota |
| Vector tiles | A fair-use limit on every plan, not a billed quota |
Pay As You Go metering
Pay As You Go bills the Transitland REST API and the Interline Routing Platform each month by use, through Stripe. Each API has free monthly usage, then a price per 1,000.
Rates are graduated: each band's price applies only to the usage within that band. For example, a month with 1,500,000 routing units bills the first 10,000 units free, the next 990,000 at $2.00 per 1,000, and the last 500,000 at $1.80 per 1,000.
Your account's billing page shows charges so far this month, and its usage page shows routing units by request type.
Routing units
Routing prices and free usage count units rather than requests. Each request counts as 1, 2, or 4 units, depending on how much work it takes. Quotas count requests, whatever their units.
| Request type | Endpoints | Units per request |
|---|---|---|
| Street routes by car, bike, foot, and other costings | valhalla/route | 1 |
| Locate and centroid | valhalla/locate, valhalla/centroid | 1 |
| Transit routing, including transit isochrones and map matching | otp/plan, otp/isochrone, otp/mapmatch | 2 |
| Street isochrones and expansion | valhalla/isochrone, valhalla/expansion | 2 |
| Street map matching | valhalla/trace_route, valhalla/trace_attributes | 2 |
| Optimized routes | valhalla/optimized_route | 4 |
| Time-distance matrix | valhalla/sources_to_targets | 4 |
Endpoints are relative to https://transit.land/api/v2/routing/. Any other street routing endpoint counts as 1 unit. A matrix request counts as 4 units however many origins and destinations it has.
Combining plans
An account holds one plan for each kind of access:
- Pay As You Go can't be combined with Hobbyist/Academic or Enterprise, since each already includes the Transitland REST API and the Interline Routing Platform.
- When a Pay As You Go subscription starts, it replaces the account's Explorer plan, and the same API key keeps working.
Attribution
Using Transitland data means agreeing to the Transitland Terms. On every plan except Enterprise and commercial Datasets licenses, that means crediting Transitland by name or logo wherever you use the data, with a link to https://www.transit.land/terms. Enterprise customers can negotiate other terms.