# QuantaFlow Google Maps Directions via x402

> QuantaFlow Google Maps Directions via x402 is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Returns Google Maps driving/transit directions between two locations, accessed via x402 micropayment protocol at $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/serp-google-maps-directions?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-google-maps-directions-via-x402-56828bf1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EcahE1vbjm1Dr-zTPyfgg

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 quantaflow-google-maps-directions-via-x402-56828bf1 -d '<json body>'
```

Example prompt: Can you get me Google Maps directions from 123 Main St, Austin TX to Austin-Bergstrom International Airport, driving mode?

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-use access to Google Maps directions data without a long-term API subscription, especially in Web3/DeFi agent workflows where x402 USDC micropayments are the preferred payment rail. Ideal for AI agents that need on-demand routing data at low cost ($0.01/call) without managing API keys.

## Known failure modes

- Missing or malformed origin/destination returns an error or empty directions
- Payment failure (insufficient USDC balance) results in 402 Payment Required response
- Invalid travel mode parameter may return unexpected results or an error
- Upstream SerpAPI/Google Maps outage causes passthrough failure
- Ambiguous address input may return incorrect or multiple candidate routes

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The upstream Google Maps/SERP directions response, passed through after successful x402 micropayment: includes route steps, distance, duration, travel mode details, and any transit or waypoint info as returned by the underlying SERP directions API.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-google-maps-directions-via-x402-56828bf1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)