Stay organized with collections
Save and categorize content based on your preferences.
Requests for the Routes API are billed under the SKU for the
features used by the request.
Click the infoinfo
icon to see the table of contents for this page.
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:
A request to Compute Routes is billed as a
single QUERY.
A request to Compute Route Matrix is billed per ELEMENT
of the request, where the number of elements is equal to: the number of
origins multiplied by the number of destinations. If a request contain
two origins and three destinations, then the single request is
billed for six elements.
A request that uses only basic features and uses a maximum of 10
intermediate waypoints is charged based on the Basic SKU.
A request that uses an advanced feature, such as the
TRAFFIC_AWARE or TRAFFIC_AWARE_OPTIMAL route
modifiers, is charged based on the Advanced SKU.
A request that uses a preferred feature, such as two-wheel routing, is
charged based on the Preferred SKU.
This SKU is triggered when you make a request to the
Compute Routes
that uses one or more of the following Pro features:
Between 11 and 25 intermediate waypoints
Waypoint optimization: Triggered by setting "optimizeWaypointOrder": "true".
Traffic aware or traffic aware optimal routing. These routing options correspond to setting the
routingPreference property in the request to
TRAFFIC_AWARE or
TRAFFIC_AWARE_OPTIMAL.
Location modifiers. When you use the following options
to indicate how drivers should approach a particular location:
This SKU is triggered for each element returned when you make a request that uses one or more of the following Pro features:
Traffic aware or traffic aware optimal routing. These routing options correspond to setting the
routingPreference property in the request to
TRAFFIC_AWARE or
TRAFFIC_AWARE_OPTIMAL.
Location modifiers. When you use the following options
to indicate how drivers should approach a particular location:
[[["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-07 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"]]
