Routes API Usage and Billing

  • The Routes API utilizes a pay-as-you-go pricing model, billing based on the specific features used in each request and falling under either Basic, Advanced, or Preferred SKUs.

  • Compute Routes requests are billed per query, while Compute Route Matrix requests are billed per element, calculated by multiplying the number of origins by the number of destinations.

  • Usage limits apply to the Routes API, including query and element rate limits per minute and maximums for waypoints, origins, destinations, and elements per request type.

  • You can manage costs by setting daily quota limits for the Routes API in the Google Cloud Console to prevent exceeding your budget and ensure continued access.

 Requests for the Routes API are billed under the SKU for the features used by the request.

Compute Routes and Compute Route Matrix each have three SKUs that determine the cost of a request. The SKU used to determine the cost is based on the service you request, Compute Routes or Compute Route Matrix, and the features that you use in the request. For example:

  • Compute Routes requests are billed for each Request.

  • Compute Route Matrix requests are billed per ELEMENT returned from the request. The number of elements is the number of origins multiplied by the number of destinations. For example, if a request contains two origins and three destinations, then the request is billed for six elements.

The features you use determine which SKU category is billed:

  • Essentials: Billed for requests that use only basic features with a maximum of 10 intermediate waypoints.

  • Pro: Billed for requests that use an advanced feature, such as the TRAFFIC_AWARE or TRAFFIC_AWARE_OPTIMAL route modifiers.

  • Enterprise: Billed for requests that use an enterprise feature, such as two-wheel routing.

See the SKU details for a complete list of features that trigger these SKUs.

SKU details and pricing for the Routes API

The following table shows the SKU details and pricing for the Routes API.

CategorySKU DetailsSKU Pricing
Essentials SKU: Routes: Compute Routes Essentials Main pricing list
India pricing list
Essentials SKU: Routes: Compute Route Matrix Essentials Main pricing list
India pricing list
Pro SKU: Routes: Compute Routes Pro Main pricing list
India pricing list
Pro SKU: Routes: Compute Route Matrix Pro Main pricing list
India pricing list
Enterprise SKU: Routes: Compute Routes Enterprise Main pricing list
India pricing list
Enterprise SKU: Routes: Compute Route Matrix Enterprise Main pricing list
India pricing list

Usage limits

The following usage limits are in place for the Routes API.

Compute Routes

  • Rate limit of 3,000 QPM queries per minute.

  • Maximum allowed number of intermediate waypoints per ComputeRoutes request is 25.

Compute Route Matrix

  • The rate limit is 3,000 EPM elements per minute, calculated by number of origins times the number of destinations.

  • Maximum allowed number of origins and destinations that you can specify by using a place ID or address is 50.

  • Maximum allowed total number of elements per ComputeRouteMatrix request with routingPreference set to TRAFFIC_AWARE_OPTIMAL is 100.

  • Maximum allowed total number of elements per ComputeRouteMatrix request with travelMode set to TRANSIT is 100.

  • Maximum allowed total number of elements per ComputeRouteMatrix request otherwise is 625.

Cost-effective strategies for the Routes API

This section provides ways to optimize your usage and reduce costs associated with the Routes API.

Limit Compute Routes waypoints

Limit user entries in a query to a maximum of 10 waypoints. Requests containing more than 10 waypoints are billed at a higher rate.

Use Compute Routes optimization for optimal routing

Requests using the waypoint optimization argument are billed at a higher rate.

The optimization argument sorts waypoints to ensure optimal routing. This means that travel from A to E is a better experience when optimized (A-B-C-D-E) versus the random sequence of a non-optimized route, such as A-D-B-C-E.

Use real-time traffic models in Compute Routes and Distance Matrix API (Legacy)

Compute Routes and Distance Matrix API (Legacy) requests that include real-time traffic models are billed at a higher rate. If traffic models are omitted from a request, the results are based solely on physical factors: roads, distance, and speed limits. Enable real-time traffic models by setting the departure time to now.

Use Route Traveled & Nearest Road when GPS data is imprecise

The Maps Roads API features, Route Traveled and Nearest Road, are included in the advanced tier and are billed at a higher rate. Use these features where GPS data is imprecise and the Roads API can help determine the correct road. Speed Limits, another feature of the Roads API, is available only to Asset Tracking customers.

Adjust quota

Quota limits define the maximum number of requests allowed for a specific API or service within a given timeframe. When the number of requests in your project reaches the quota limit, your service stops responding to requests.

To modify a quota value for your API, follow these steps:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to modify the quota.
  3. Identify the quota value that you want to change, and select it using the checkbox.
  4. Click Edit, enter a new quota value, and click Submit request.

View quota increase requests

To view all quota increase requests, including past and pending requests:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to view the quota increase request.
  3. Click Increase Requests.

Terms of Use restrictions

For complete details on allowed usage, consult the License Restrictions section in the Google Maps Platform Terms of Service.