# Waze Venues by Bounding Box

> Waze Venues by Bounding Box 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).

Retrieves Waze venue data (places, areas, points of interest) within a specified geographic bounding box

## Facts

- Endpoint: GET https://x402.openwebninja.com/realtime-local-and-maps-data/waze/venues
- 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/waze-venues-by-bounding-box-18db86f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NVsPNYYrYUfUlyneZl2dS

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 waze-venues-by-bounding-box-18db86f2
```

Example prompt: Show me all Waze venues in downtown Chicago — search within the bounding box from bottom-left 41.8700,-87.6400 to top-right 41.8900,-87.6200, filtering for restaurant categories.

## When to prefer this

Use this endpoint when you need structured venue/POI data from Waze for a specific geographic bounding box, especially when you want Waze-specific metadata like approval status, Waze categories, and geometry, or when you need to cross-reference with Google Place IDs. Prefer this over generic map APIs when Waze data quality and category tagging are important for navigation or local discovery use cases.

## Known failure modes

- Missing required bottom_left or top_right query parameters returns a validation error
- Malformed coordinate strings cause parsing errors
- Bounding box too large may return truncated or empty results
- Invalid category filter strings may return no matching venues
- Zoom level out of range may affect result granularity or return an error
- Network or upstream Waze data unavailability returns a 5xx error

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

An array of venue objects each containing the venue name, unique Waze venue ID, country and state, GeoJSON geometry (Point or Polygon with coordinates), category tags, approval status, residential flag, opening hours (when available), and matched Google Place IDs.

## 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/waze-venues-by-bounding-box-18db86f2/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)