Routes API Usage and Billing

Reminder: To use the Routes API, you must enable billing on each of your projects and include an API key or OAuth token with all API or SDK requests.

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.

Category	SKU Details	SKU 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

Other usage limits

To review and manage your quotas and usage limits, see Quotas and quota alerts.

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 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.

Terms of Use restrictions

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

---