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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-26 UTC."],[[["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."]]],["The Routes API uses a pay-as-you-go model, billed by SKU based on the features used. To use the API, enable billing and include an API key or OAuth token. Requests are categorized as Compute Routes or Compute Route Matrix, with Basic, Advanced, and Preferred SKUs, determined by features like traffic awareness or two-wheel routing. Costs are calculated per query or element, with varying monthly volume ranges. Usage limits apply, including rate limits and maximum waypoints/origins/destinations. Manage costs by setting daily quota limits. A $200 monthly credit is available until Feb 28, 2025.\n"]]