Compute Routes y Compute Route Matrix tienen tres SKU cada uno que determinan el costo de una solicitud. El SKU que se usa para determinar el costo se basa en el servicio que solicitas, ya sea Compute Routes o Compute Route Matrix, y en las funciones que usas en la solicitud.
Por ejemplo:
Las solicitudes a Compute Routes se facturan por cada solicitud.
Las solicitudes a Compute Route Matrix se facturan por cada ELEMENT que se devuelve en la respuesta. La cantidad de elementos es la cantidad de orígenes multiplicada por la cantidad de destinos. Por ejemplo, si una solicitud contiene dos orígenes y tres destinos, se facturarán seis elementos.
Las funciones que usas determinan la categoría de SKU que se factura:
Básica: Se factura por las solicitudes que usan solo funciones básicas con un máximo de 10 puntos de referencia intermedios.
Pro: Se factura por las solicitudes que usan una función avanzada, como los modificadores de ruta TRAFFIC_AWARE o TRAFFIC_AWARE_OPTIMAL.
Enterprise: Se factura por las solicitudes que usan una función empresarial, como la generación de rutas para vehículos de dos ruedas.
Consulta los detalles del SKU para obtener una lista completa de las funciones que activan estos SKU.
Detalles y precios de los SKU de la API de Routes
En la siguiente tabla, se muestran los detalles y los precios de los SKU de la API de Routes.
Se aplican los siguientes límites de uso a la API de Routes.
Compute Routes
Límite de frecuencia de 3,000 QPM por minuto
La cantidad máxima permitida de puntos de referencia intermedios por solicitud de ComputeRoutes es de 25.
Compute Route Matrix
El límite de frecuencia es de 3,000 elementos por minuto, que se calcula multiplicando la cantidad de orígenes por la cantidad de destinos.
La cantidad máxima permitida de orígenes y destinos que puedes especificar con un ID de lugar o una dirección es de 50.
La cantidad total máxima permitida de elementos por solicitud de ComputeRouteMatrix con routingPreference establecido en TRAFFIC_AWARE_OPTIMAL es de 100.
La cantidad total máxima permitida de elementos por solicitud de ComputeRouteMatrix con travelMode establecido en TRANSIT es de 100.
De lo contrario, la cantidad total máxima permitida de elementos por solicitud de ComputeRouteMatrix es de 625.
Ajustar cuota
Los límites de cuota definen la cantidad máxima de solicitudes permitidas para una API o un servicio específicos dentro de un período determinado. Cuando la cantidad de solicitudes en tu proyecto alcanza el límite de cuota, tu servicio deja de responder a las solicitudes.
Para modificar el valor de una cuota de tu API, sigue estos pasos:
En la consola de Cloud, navega a Google Maps Platform > Cuotas.
Selecciona la API para la que deseas modificar la cuota.
Identifica el valor de la cuota que deseas cambiar y selecciónalo con la casilla de verificación.
Haz clic en Editar, ingresa un valor de cuota nuevo y haz clic en Enviar solicitud.
Consulta las solicitudes de aumento de cuota
Para ver todas las solicitudes de aumento de cuota, incluidas las solicitudes pendientes y anteriores, sigue estos pasos:
En la consola de Cloud, navega a Google Maps Platform > Cuotas.
Selecciona la API para la que deseas ver la solicitud de aumento de cuota.
Haz clic en Solicitudes de aumento.
Restricciones de las Condiciones de Uso
Para obtener información detallada sobre el uso permitido, consulta la sección Restricciones de licencia en las Condiciones del Servicio de Google Maps Platform.
[null,null,["Última actualización: 2025-08-06 (UTC)"],[[["\u003cp\u003eThe 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.\u003c/p\u003e\n"],["\u003cp\u003eCompute 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.\u003c/p\u003e\n"],["\u003cp\u003eUsage 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.\u003c/p\u003e\n"],["\u003cp\u003eYou 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.\u003c/p\u003e\n"]]],["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"],null,["# Routes API Usage and Billing\n\n| **Reminder:** To use the Routes API, you must [enable billing](https://console.cloud.google.com/project/_/billing/enable?utm_source=Docs_BillingNudge) on each of your projects and include an [API key](/maps/documentation/routes/get-api-key) or OAuth token with all API or SDK requests.\nRequests for the Routes API are billed under the SKU for the [features used by the request](#pricing-for-product).\n\n\u003cbr /\u003e\n\n[Compute Routes](/maps/documentation/routes/compute_route_directions) and\n[Compute Route Matrix](/maps/documentation/routes/compute_route_matrix) each have three SKUs\nthat determine the cost of a request. The SKU used to determine the cost is\nbased on the service you request, Compute Routes or\nCompute Route Matrix, and the features that you use in the request.\nFor example:\n\n- **Compute Routes** requests are billed for each\n **Request**.\n\n- **Compute Route Matrix** requests are billed per **ELEMENT**\n returned from the request. The number of elements is the number of\n origins multiplied by the number of destinations. For example, if\n a request contains **two** origins and **three** destinations, then\n the request is billed for **six** elements.\n\nThe features you use determine which SKU category is billed:\n\n- **Essentials**: Billed for requests that use only basic features with\n a maximum of 10 intermediate waypoints.\n\n- **Pro** : Billed for requests that use an advanced feature, such as the\n `TRAFFIC_AWARE` or `TRAFFIC_AWARE_OPTIMAL` route modifiers.\n\n- **Enterprise**: Billed for requests that use an enterprise feature,\n such as two-wheel routing.\n\nSee the SKU details for a complete list of features that trigger these SKUs.\n\nSKU details and pricing for the Routes API\n------------------------------------------\n\nThe following table shows the SKU details and pricing for the Routes API.\n\n| Category | SKU Details | SKU Pricing |\n|----------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Essentials** | [SKU: Routes: Compute Routes Essentials](/maps/billing-and-pricing/sku-details#compute-routes-ess-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n| **Essentials** | [SKU: Routes: Compute Route Matrix Essentials](/maps/billing-and-pricing/sku-details#compute-route-matrix-ess-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n| **Pro** | [SKU: Routes: Compute Routes Pro](/maps/billing-and-pricing/sku-details#compute-routes-pro-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n| **Pro** | [SKU: Routes: Compute Route Matrix Pro](/maps/billing-and-pricing/sku-details#compute-route-matrix-pro-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n| **Enterprise** | [SKU: Routes: Compute Routes Enterprise](/maps/billing-and-pricing/sku-details#compute-routes-ent-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n| **Enterprise** | [SKU: Routes: Compute Route Matrix Enterprise](/maps/billing-and-pricing/sku-details#compute-route-matrix-ent-sku) | [Main pricing list](/maps/billing-and-pricing/pricing#routes-pricing) [India pricing list](/maps/billing-and-pricing/pricing-india#routes-pricing) |\n\n\nUsage limits\n------------\n\nThe following\nusage limits are in place for the Routes API.\n\n### Compute Routes\n\n- Rate limit of 3,000 QPM queries per minute.\n\n- Maximum allowed number of intermediate waypoints per `ComputeRoutes` request\n request is 25.\n\n### Compute Route Matrix\n\n- The rate limit is 3,000 EPM elements per minute, calculated by\n number of origins times the number of destinations.\n\n- Maximum allowed number of origins and destinations that you can specify\n by using a place ID or address is 50.\n\n- Maximum allowed total number of elements per\n `ComputeRouteMatrix` request with `routingPreference` set to\n `TRAFFIC_AWARE_OPTIMAL` is 100.\n\n- Maximum allowed total number of elements per\n `ComputeRouteMatrix` request with `travelMode` set to `TRANSIT` is 100.\n\n- Maximum allowed total number of elements per\n `ComputeRouteMatrix` request otherwise is 625.\n\n\nAdjust quota\n------------\n\n\nQuota limits define the maximum number of requests allowed for a specific API or service within a\ngiven timeframe. When the number of requests in your project reaches the quota limit, your service\nstops responding to requests.\n| **Important:** To understand how an increase in quota could affect your bill, check out the [pricing calculator](https://mapsplatform.google.com/pricing/#pricing-calculator).\n\nTo modify a quota value for your API, follow these steps:\n\n1. In the Cloud console, navigate to **Google Maps Platform \\\u003e Quotas**.\n2. Select the API for which you want to modify the quota.\n3. Identify the quota value that you want to change, and select it using the checkbox.\n4. Click **Edit** , enter a new quota value, and click **Submit request**.\n\n### View quota increase requests\n\n| **Important:** You must have the appropriate [IAM permissions to view quota increase requests](https://cloud.google.com/docs/quotas/permissions#permissions_increase).\n\nTo view all quota increase requests, including past and pending requests:\n\n1. In the Cloud console, navigate to **Google Maps Platform \\\u003e Quotas**.\n2. Select the API for which you want to view the quota increase request.\n3. Click **Increase Requests**.\n\n| **Tip:** Make sure to monitor your quota usage regularly to avoid service interruptions. [Learn more about quotas and\n| quota alerts](/maps/billing-and-pricing/manage-costs#quotas).\n\n\u003cbr /\u003e\n\nTerms of Use restrictions\n-------------------------\n\nFor complete details on allowed usage, consult the\n[License Restrictions section](https://cloud.google.com/maps-platform/terms/#3.-license.)\nin the Google Maps Platform Terms of Service.\n\n\n*** ** * ** ***"]]