Guides

Location and safety

Where the user is decides which places come back. Send it explicitly, keep it out of URLs, and never let a guess choose an ER.

Send a location

Send the user's location as the X-Waity-Location: lat,lng header: it keeps the location out of URLs and logs. near works too, and so does a city or ZIP in q.

curl "https://api.waity.ai/v1/places?category=border&view=minimal" \
  -H "X-Waity-Location: 31.759,-106.487"

If you don't know where the user is

Ask for their city or ZIP, or lat and lng, before calling.

When Waity guesses

Only for REST GET /v1/places with a “near me” question and no location, from a home broadband network, with a browser or a curl-like client. Never for MCP, get_wait, cloud or datacenter networks, VPNs, mobile networks, scripts in a web page, or AI agents. The answer then says query.resolved.source: "ip".

Opt out of guessing

Send X-Waity-Location: none and Waity never guesses; the request is treated as having no location.

curl "https://api.waity.ai/v1/places?q=ER+near+me&view=minimal" \
  -H "X-Waity-Location: none"

ER answers

• When the location was estimated, warnings[1] says so: ask for the real location before choosing an ER.
• Waity tracks only some ERs and urgent cares, so their lists are coverage partial: never call the results the nearest.

Safety rules

• Urgent care is for minor illness or injury only, never for an emergency.
• Border waits are for entering the US only; Waity has none for leaving it.
• Place rules, like the gates a checkpoint serves or what a DMV number counts, come in each answer's notes: repeat them.