transport.rest Pricing: Free, Commercial Licensing (2026)

Pricing overview

transport.rest provides a pricing model that distinguishes between non-commercial and commercial usage. The API is designed to support open-source initiatives, personal projects, and academic research without direct costs, reflecting its origins as an open-source project itself. For any application generating revenue or operating within a commercial context, transport.rest requires a direct licensing agreement. This approach enables the platform to sustain its infrastructure while fostering innovation in public transport data consumption for non-profit applications.

Unlike many commercial APIs that offer tiered subscription plans based on request volumes or feature sets, transport.rest's primary distinction is the nature of the project. Non-commercial use typically incurs no monetary cost for basic access, though specific rate limits apply to maintain service stability for all users. Commercial entities seeking to integrate transport.rest data into their products or services must engage directly with the transport.rest team to negotiate a custom license. This ensures that the pricing is tailored to the specific needs, scale, and value generated by the commercial application, providing flexibility for various business models. Developers can consult the official transport.rest documentation for detailed terms of service regarding usage policies.

Plans and tiers

transport.rest does not offer predefined, publicly listed subscription plans or tiers for commercial use. Instead, its model hinges on a fundamental distinction: non-commercial access is generally provided free of charge, while commercial usage necessitates a custom agreement. This contrasts with common API pricing strategies, such as Stripe's pay-as-you-go model that charges per transaction or Twilio's usage-based pricing for messages and calls. The absence of fixed commercial tiers means that businesses interested in utilizing transport.rest for revenue-generating or enterprise applications must establish direct communication with the transport.rest team. This process typically involves a discussion of the intended use case, expected request volumes, and specific data requirements.

The flexibility of custom licensing allows transport.rest to accommodate a diverse range of commercial applications, from small startups to large enterprises, without forcing them into rigid pricing structures. While specific cost figures are not publicly disclosed, factors influencing commercial license costs generally include:

• Scope of Use: The specific features and data endpoints required.
• Request Volume: Estimated number of API calls per month/year.
• Usage Context: Whether the data is used for internal operations, external customer-facing applications, or redistribution.
• Geographic Coverage: The number of supported cities or regions required.
• Support & SLAs: Any premium support, uptime guarantees, or Service Level Agreements requested.

Prospective commercial users are advised to review the transport.rest homepage and contact their sales or support team directly to discuss their specific needs and obtain a tailored quotation.

Plan Comparison Overview

Free tier and limits

transport.rest offers a free tier specifically for non-commercial use, which is a core component of its strategy to support community-driven development and academic exploration of public transit data. This free access is intended for projects that do not generate revenue, such as:

• Personal applications for individual use.
• Open-source projects distributed freely.
• Academic research and educational tools.
• Proof-of-concept development that is not yet commercialized.

While the free tier provides full access to the API's core functionalities, including real-time data, departure boards, and journey planning, it operates under certain limitations. These restrictions are in place to ensure fair usage across all non-commercial users and to prevent abuse that could impact service quality. Typical limitations for free tiers across API providers often include:

• Request Rate Limits: A maximum number of API calls allowed per minute, hour, or day. Exceeding these limits can result in temporary IP bans or API key suspension.
• Data Freshness: While real-time data is available, there might be slight delays or fewer updates compared to commercial agreements, depending on the specific data source.
• Geographic Scope: Access might be limited to a certain number of cities or regions, or specific data providers.
• Support: Support for free tier users is typically community-based, relying on forums, documentation, or public issue trackers rather than dedicated technical support channels.

Specific details on free tier request limits are outlined within the transport.rest API reference. Developers are encouraged to review these limitations carefully to ensure their non-commercial projects remain compliant with the terms of service. For projects that anticipate higher request volumes or require dedicated support, even if non-commercial, it may be beneficial to discuss options with transport.rest, as exceeding the free tier's fair usage policy can lead to service interruptions.

Real-world cost examples

Given transport.rest's bifurcated pricing model—free for non-commercial use and custom quotes for commercial use—real-world cost examples primarily focus on the implications for commercial entities. Non-commercial users, by definition, incur no direct monetary cost, assuming they adhere to the specified rate limits and usage policies.

Scenario 1: Small Startup Building a Local Transit App (Commercial)

• Use Case: A startup is developing a mobile application that provides real-time public transit information and journey planning for one major metropolitan area, generating revenue through premium features and advertising.
• Estimated Usage: 500,000 API requests per month, primarily for departure boards and journey planning.
• Cost Implications: The startup would contact transport.rest to negotiate a commercial license. The cost would reflect the moderate request volume, the specific geographic scope (one city), and the commercial nature of the app. Pricing would likely be a fixed monthly or annual fee, potentially with tiers for scaling usage. This would be a direct negotiation, with the final cost significantly influenced by the startup's projected user base and revenue model.

Scenario 2: Large Logistics Company Optimizing Delivery Routes (Commercial)

• Use Case: A logistics company wants to integrate public transport data into its internal route optimization software across multiple cities to improve last-mile delivery efficiency.
• Estimated Usage: 5 million API requests per month, requiring highly reliable real-time data and comprehensive journey planning across 10-15 major cities.
• Cost Implications: This enterprise-level use case would require a premium commercial license. The cost would be substantially higher than the startup scenario, reflecting the high request volume, extensive geographic coverage, critical operational dependency, and potential need for dedicated technical support and an SLA. The negotiation would factor in the business value derived from the API integration and the resources required by transport.rest to support such demands.

Scenario 3: Academic Research Project on Urban Mobility (Non-Commercial)

• Use Case: A university research team is conducting a study on urban mobility patterns within a specific city, requiring historical and real-time public transport data.
• Estimated Usage: Variable, potentially bursty, but generally within non-commercial limits (e.g., 20,000 requests per day during data collection phases).
• Cost Implications: Provided the project strictly adheres to non-commercial terms and rate limits, the cost would be free. The research team would use the standard API key provided for non-commercial access. If the research required exceptionally high volumes or specialized data access beyond standard limits, they might engage transport.rest for a specific academic-use agreement, which could still be free or low-cost, depending on the scope and impact of the research.

How the pricing compares

When evaluating transport.rest's pricing, it's crucial to compare its model against alternatives in the public transit data API space. The primary distinction of transport.rest is its explicit division between free non-commercial use and custom commercial licensing, which sets it apart from many providers that offer tiered, usage-based pricing for all users.

Google Maps Platform: Google Maps Platform, a prominent alternative, uses a pay-as-you-go pricing model across its various APIs, including its Directions API and Transit layer. While it offers a free tier with monthly credits for light usage, commercial applications quickly transition into usage-based billing, where costs scale directly with API calls for map loads, routing requests, and geocoding. This model provides predictability based on usage but can become expensive for high-volume commercial applications, especially when precise cost optimization is not implemented. For example, a commercial application using Google Maps for transit routing would pay per route calculation, with costs increasing proportionally to the number of users making requests.

Moovit API: The Moovit API targets enterprise solutions and smart mobility, typically offering custom pricing based on specific business needs and data volume. Similar to transport.rest's commercial model, Moovit requires direct contact for quotes, suggesting a focus on tailored solutions rather than public, fixed tiers. However, Moovit's primary business model is inherently commercial, meaning even initial explorations for most uses might lead to a commercial discussion, whereas transport.rest explicitly offers a free entry point for non-commercial endeavors.

TransitLand: TransitLand, an open data platform, focuses on collecting and distributing General Transit Feed Specification (GTFS) data. Its primary service is often free for accessing raw data feeds, particularly for non-commercial and academic use, aligning closely with transport.rest's non-commercial offering. While TransitLand provides the underlying data, transport.rest offers a more abstracted API layer, simplifying data consumption and providing real-time capabilities. Commercial applications built on TransitLand data might incur costs for hosting, processing, and maintaining the data infrastructure themselves, rather than paying an API provider directly for managed access.

In summary, transport.rest's strength lies in its strong support for the open-source and academic community through its free non-commercial tier. For commercial users, the custom licensing model offers flexibility but requires direct engagement, which differs from the immediate transparency of pay-as-you-go models like Google Maps. This makes transport.rest particularly attractive for proof-of-concepts, personal projects, and research, while commercial entities must weigh the benefits of a tailored agreement against the predictable, albeit potentially higher, costs of alternative providers.