# OpenWeb Ninja Waze Driving Directions API

> OpenWeb Ninja Waze Driving Directions API is a paid API for AI agents from x402.openwebninja.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-16).

Returns real-time Waze driving directions and route data between two locations, including turn-by-turn navigation, travel time, and traffic conditions.

## Facts

- Endpoint: GET https://x402.openwebninja.com/realtime-local-and-maps-data/waze/driving-directions
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openweb-ninja-waze-driving-directions-api-0b048328
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nuUyeP5sSafn2ea25JPOA

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 openweb-ninja-waze-driving-directions-api-0b048328
```

Example prompt: Can you get me Waze driving directions from 123 Main Street, San Francisco to SFO airport right now, including current traffic conditions?

## When to prefer this

Choose this endpoint when you need real-time, traffic-aware driving directions sourced specifically from Waze crowd-sourced data, with no API key or account setup required. It is ideal for lightweight, per-call use cases where you want fresh route data without maintaining a mapping API subscription. Prefer over Google Maps or Mapbox APIs when you want Waze-specific routing logic and pay-as-you-go micropayment billing.

## Known failure modes

- Invalid or unrecognizable origin/destination addresses return an error or empty result
- No route found between locations (e.g., different continents without ferry/tunnel)
- Waze data temporarily unavailable causing timeout or empty response
- Ambiguous address strings causing incorrect routing
- Payment failure via x402 preventing request from being processed

## How this service works

40+ public web-data, SERP, e-commerce, real-estate, finance and AI-search APIs, payable per call over x402 (USDC on Base, Polygon, Arbitrum). No account or API key required. Most endpoints $0.003; AI-model endpoints $0.005.

## Output

Returns a JSON object containing Waze-sourced driving route data, including step-by-step turn-by-turn directions, total distance, estimated travel time accounting for current traffic, alternative routes if available, and any traffic alerts or incidents along the route.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openweb-ninja-waze-driving-directions-api-0b048328/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.openwebninja.com](https://www.zero.xyz/host/x402.openwebninja.com/llms.txt)