Guides

Call the REST API

Two GET routes and one answer shape. Any HTTP client works, and any browser origin may call it.

Base URL

https://api.waity.ai

Find places

GET /v1/places

Give one of: a location (near=lat,lng or the X-Waity-Location header), q (a place name, city, airport code, ZIP or a plain ask like “ER near Brooklyn”), or ids. Optional: category, open, sort, limit and view.

curl "https://api.waity.ai/v1/places?q=El+Paso&category=border&view=minimal"

One place

GET /v1/places/{id}

Optional: under (minutes), travel_min (adds next.leave_by), date (up to 7 days ahead), forecast and view. An airport, border port or hospital campus id returns its lanes or departments.

curl "https://api.waity.ai/v1/places/pl_xaed7pr1f5?travel_min=15&view=minimal"

Authentication

Calls work without a key. With a key, send it as X-Api-Key or Authorization: Bearer.

curl "https://api.waity.ai/v1/places/pl_xaed7pr1f5?view=minimal" \
  -H "X-Api-Key: $WAITY_API_KEY"

Views

view=minimal returns the essentials and is a strict subset of the full view: same keys, same paths, fewer of them. The MCP tools default to it.

Reference

Every route, parameter and response is in the API reference; the schema is openapi.json.