# Waze Venues Lookup by Bounding Box

> Waze Venues Lookup 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-15).

Returns Waze venue data (places, areas, water bodies, etc.) within a specified geographic bounding box

## Facts

- Endpoint: GET https://x402.openwebninja.com/waze/venues
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/waze-venues-lookup-by-bounding-box-66551579
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dGJFX0A2HgLZXAG-JyQrL

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-lookup-by-bounding-box-66551579
```

Example prompt: Find me all Waze venues inside the bounding box from bottom-left 37.7749,-122.4294 to top-right 37.8044,-122.4069 — filter by restaurants if possible and use zoom level 15.

## When to prefer this

Use this endpoint when you need Waze-sourced venue data (with Waze approval status, Waze categories, and GeoJSON geometry) for a specific geographic bounding box. Prefer this over generic POI APIs when you need Waze-specific metadata like moderator approval status or Waze category tags, or when you want to cross-reference with Google Place IDs. Ideal for map-based applications needing venue polygons rather than just point coordinates.

## Known failure modes

- Missing required bottom_left or top_right query params returns a 400/422 error
- Invalid coordinate format causes a parsing error
- Very large bounding box may return truncated or empty results
- Payment failure (insufficient USDC balance) returns HTTP 402
- Rate limiting may cause intermittent failures
- Zoom level out of valid range may produce unexpected results

## 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: venue_id, name, country, state, geometry (GeoJSON Point or Polygon with coordinates), categories (Waze tags), approved status, residential flag, opening_hours, and google_place_ids. Data represents venues physically located within the requested bounding box.

## 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-lookup-by-bounding-box-66551579/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)