Pricing overview

Transport for Czech Republic, operating under the Public Integrated Transport (PID) system, offers its data and API access with a model centered on accessibility for developers and public benefit. The primary approach is to provide free access for most standard applications, particularly those focused on enhancing public transport information and services within the Czech Republic. This includes access to critical data feeds like General Transit Feed Specification (GTFS) and GTFS Realtime (GTFS-RT), as well as a dedicated HTTP API for departures, stops, and connections.

While the initial access is free, the PID system acknowledges that certain high-volume or commercial applications may require specific agreements. These custom agreements are designed to ensure sustainable service provision and may involve bespoke terms based on usage scale, data consumption, and the commercial nature of the project. Developers are required to request an API key to gain access to the data, which facilitates monitoring and management of usage, enabling the PID team to identify applications that might fall under the custom agreement category. Further details on data access and API integration are available in the official PID API and Data documentation.

Plans and tiers

Transport for Czech Republic's pricing structure is primarily divided into two conceptual tiers: a widely available free tier for standard use and custom agreements for more demanding applications. There are no explicitly published tiered plans with fixed prices or usage quotas in the manner of many commercial API providers. Instead, the distinction is made based on the nature and scale of the integration.

The core offering includes access to:

  • GTFS Feed: Static data about routes, stops, schedules, and fares.
  • GTFS-RT Feed: Real-time updates on vehicle positions, trip updates, and service alerts.
  • HTTP API: Programmatic access to real-time departures, stop information, and connection details.

Access to these resources generally requires an API key, which can be requested through the official PID channels. The distinction between the free tier and custom agreements is not based on a specific numerical threshold of requests per second or daily data transfer, but rather on an evaluation of the project's scope and potential impact on the PID infrastructure. Projects that are deemed to be very high-volume, resource-intensive, or primarily commercial in nature are encouraged to contact PID directly to discuss a tailored agreement. This flexible approach allows PID to support a broad range of innovative applications while managing its infrastructure resources effectively. Developers seeking to understand the implications for their specific project should consult the PID data and API integration guide for details on requesting access and potential usage guidelines.

Transport for Czech Republic Data Access Overview
Plan/Tier Price Key Limits/Conditions Best For
Standard Free Access Free API key required; generous limits for non-commercial, standard usage. Subject to fair use policy. Public transport application development, personal projects, academic research, real-time passenger information systems for public benefit.
Custom Agreement (Commercial/High-Volume) Negotiated (may involve fees) Specific terms negotiated based on project scope, usage volume, and commercial intent. Large-scale commercial applications, enterprise solutions, high-frequency data polling, projects requiring dedicated support or infrastructure.

Free tier and limits

Transport for Czech Republic operates with a generous free tier for accessing its public transport data and APIs. This tier is designed to support a wide array of applications, from individual developer projects to public-facing information systems. Access to the GTFS feeds (static and real-time) and the HTTP API for departures and connections is provided without direct monetary cost for standard use cases. Developers must request an API key to utilize these resources.

While specific numerical rate limits (e.g., requests per second, daily call quotas) are not explicitly published for the free tier, usage is subject to a fair use policy. This policy is intended to prevent abuse, ensure service stability for all users, and manage infrastructure load. Applications that exhibit extremely high request volumes, rapid polling frequencies that exceed typical real-time update needs, or behaviors that could negatively impact service availability may be contacted by the PID team to discuss adjustments or a transition to a custom agreement.

The free tier is particularly suitable for:

  • Developing mobile or web applications that display real-time public transport information.
  • Creating journey planners or wayfinding tools.
  • Academic research projects analyzing public transport patterns.
  • Integrations for public displays at transport hubs or community centers.

The spirit of the free tier is to foster innovation and improve public access to transport information. Developers are encouraged to design their applications to be efficient in their data requests and only fetch data as frequently as necessary (e.g., polling GTFS-RT feeds at a reasonable interval, rather than continuously). For guidance on efficient API usage, resources like the Google Transit GTFS Realtime best practices can offer valuable insights, even if specific to Google's implementation, as the underlying principles of efficient data consumption apply broadly to GTFS-RT feeds.

Real-world cost examples

Given Transport for Czech Republic's pricing model, which largely relies on a free tier with custom agreements for high-volume or commercial use, most real-world scenarios will incur no direct monetary cost for API access. However, it is important to consider indirect costs and potential scenarios where a custom agreement might be necessary.

Scenario 1: Small independent developer building a mobile app

  • Project: A developer creates a free Android/iOS application that displays real-time departures for specific stops in Prague and integrates a basic journey planner using static GTFS data.
  • Usage: The app has 5,000 active users, each checking departures a few times a day. GTFS-RT data is polled every 30 seconds for active routes.
  • Cost: Free. This usage falls well within the generous free tier. The API key request is the only required step for access. The developer's primary costs would be for app development, hosting, and distribution, not for PID data access.

Scenario 2: University research project

  • Project: A university team is analyzing historical public transport performance and real-time disruptions over a six-month period for academic research. They require bulk downloads of GTFS data and frequent access to GTFS-RT for capturing real-time events.
  • Usage: Automated scripts download GTFS feeds regularly and poll GTFS-RT every 10 seconds across all routes during peak hours for data collection.
  • Cost: Free. As an academic, non-commercial project focused on public benefit, this usage is typically accommodated within the free tier. The team would need to request an API key and potentially communicate their project scope to PID to ensure their polling frequency aligns with fair use guidelines.

Scenario 3: Commercial enterprise solution for logistics

  • Project: A logistics company develops an internal system to optimize last-mile delivery routes, integrating PID real-time data to predict public transport delays that might affect their couriers using public transport. The system requires constant, high-frequency polling across a wide geographical area.
  • Usage: The system makes thousands of API requests per minute, 24/7, to monitor vehicle positions and potential disruptions for hundreds of routes simultaneously.
  • Cost: Potentially subject to a custom agreement. Due to the high-volume, commercial nature, and continuous polling, this scenario likely exceeds the standard free tier. The company would need to engage directly with Transport for Czech Republic to negotiate a custom agreement. This agreement might involve a fee, specific service level agreements (SLAs), or dedicated access points to prevent impact on other free tier users.

Scenario 4: Public information display network

  • Project: A city council deploys a network of 50 digital displays at bus stops and public buildings, showing real-time departure information for nearby stops.
  • Usage: Each display polls the real-time API every 15-30 seconds for its specific set of stops.
  • Cost: Free. This is a classic public benefit application. Even with 50 displays, the localized and relatively infrequent polling per display would typically fall within the free tier, assuming efficient API usage. An API key would be required for the entire network.

How the pricing compares

Transport for Czech Republic's pricing model, centered on free access for most use cases with custom agreements for high-volume or commercial applications, is common among public transit authorities globally. This approach contrasts with fully commercialized API providers and some private data aggregators.

Comparison with Commercial API Providers:

  • Google Maps Platform (Transit API): While Google Maps offers extensive transit data, its pricing model is usage-based, with costs accumulating per API call or data request after a free credit. For example, the Directions API (which can include transit) charges per request. For developers building on Google Maps, this means direct monetary costs for significant usage, whereas PID data access is free for similar core functionalities.
  • HERE Technologies (Transit API): Similar to Google, HERE provides a comprehensive suite of mapping and transit APIs, but operates on a commercial pay-as-you-go model or enterprise licensing. While offering global coverage and advanced features, direct costs are incurred for API calls, data volumes, and specific services.
  • Private Data Aggregators: Companies that aggregate and standardize transit data from multiple sources often charge subscription fees or per-query costs for access to their curated datasets and APIs. These services might offer broader geographical coverage or enhanced data quality/consistency, but at a direct financial cost.

Comparison with Other Public Transit Authorities:

  • Many major cities and regions, such as Transport for London (TfL) and Metropolitan Transportation Authority (MTA) in New York, also offer free API access to their respective public transport data. This aligns with a global trend of open data initiatives to foster innovation and improve public services. However, specific usage policies, rate limits, and the process for requesting API keys can vary.
  • The underlying data format, GTFS, is a widely adopted open standard for public transport schedules and associated geographic information. Its real-time extension, GTFS-RT, provides dynamic updates. The use of these open standards by Transport for Czech Republic means that developers can leverage existing tools and libraries, reducing integration effort, which is an indirect cost saving. The GTFS specification itself is freely available and maintained by Google.

In summary, Transport for Czech Republic's pricing model is highly competitive for applications focused on the Czech Republic's public transport system. Its free-first approach significantly lowers the barrier to entry for developers and organizations compared to commercial alternatives, reserving custom agreements for specialized, high-impact commercial use cases where dedicated resources or support might be needed.