# Google Maps V2:ComputeRoutes

> Google Maps V2:ComputeRoutes is a paid API for AI agents from Google Maps at googlemaps.mpp.tempo.xyz, paid per call via MPP, $0.005/call, status unknown (last checked 2026-10-12).

Computes a detailed route between an origin and destination using Google Maps routing engine, returning turn-by-turn directions, distance, and travel time.

## Facts

- Endpoint: POST https://googlemaps.mpp.tempo.xyz/routes/directions/v2:computeRoutes?utm_source=zero.xyz
- Price: $0.005/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Provider: Google Maps
- Docs: https://developers.google.com/maps
- Website: https://developers.google.com/maps
- Tags: maps, google, geocoding, directions, places, routes, tiles, weather, air-quality, solar, roads, pollen, geolocation, aerial, validation, data
- Canonical page: https://www.zero.xyz/c/google-maps-v2-computeroutes-87586bc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4lowdbVSHMGYtUnLEjCYY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability google-maps-v2-computeroutes-87586bc0 -d '<json body>'
```

Example prompt: Can you get me driving directions from the Empire State Building in New York to Penn Station, avoiding tolls, and tell me the total distance and estimated travel time?

## When to prefer this

Use this endpoint when you need a detailed, single route with full turn-by-turn directions, polyline geometry, and rich metadata. Prefer this over the Directions JSON endpoint for newer features and structured proto-based responses. Use V2:ComputeRouteMatrix instead when you need distances/times for multiple origin-destination pairs simultaneously.

## Known failure modes

- No route found between origin and destination (e.g., islands with no road connection)
- Invalid or unresolvable location input returns geocoding error
- Unsupported travel mode for the given route returns error
- API quota exceeded or invalid credentials returns 401/403
- Departure time in the past may return non-traffic-aware results

## How this service works

Compute routes between locations

## Output

Returns a detailed route object including one or more route legs with step-by-step navigation instructions, total distance in meters, total duration in seconds, an encoded polyline for the full path, and metadata such as toll information and traffic-aware travel times.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "location",
  "size",
  "heading",
  "pitch"
 ],
 "properties": {
  "size": {
   "type": "string"
  },
  "pitch": {
   "type": "string"
  },
  "heading": {
   "type": "string"
  },
  "location": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/google-maps-v2-computeroutes-87586bc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from googlemaps.mpp.tempo.xyz](https://www.zero.xyz/host/googlemaps.mpp.tempo.xyz/llms.txt)