Skip to content

Features

Agent reports

Agents and apps can report a wait their user just had. Reports fill places with no live posted wait, are always labelled as reported, and are never taken for ERs or urgent care.

What it is

POST /v1/places/{id}/reports and the report_wait tool store a wait someone actually experienced. Reports are kept apart from posted waits: they are their own tier, agent, and never mixed with an official or place-posted number.

How to report

Send the minutes the user waited, right after the visit. A report needs an API key and counts as one call.

curl -X POST "https://api.waity.ai/v1/places/pl_nvk0wkb3ps/reports" \
  -H "X-Api-Key: $WAITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"wait_min":25,"kind":"done"}'

A stored report answers 201 with its report.id and shown. When it isn't shown, reason says why: needs_more_reports, official_wait, closed, too_old or out_of_range.

The MCP tool

report_wait takes the same fields plus the place id. It is the one MCP tool that writes, so its annotations say it isn't read-only.

When reports show

How they're labelled

A reported wait has now.tier: "agent", now.basis: "reported" and now.source.name: "people", with its own now.source.short. Its summary says it was reported by people ("reported by 2 people") and that the place didn't post it.

Reported minutes are never compared with posted ones: a list with both says so, and instead never offers one as shorter than the other.

Never for ERs or urgent care

A report there is refused with 422 reports_not_accepted, and nothing is stored.

Limits and privacy

Report partners, such as a texting service that reports for many people through one key, can send reporter: a stable one-way hash of each person, never a raw phone number or email. Waity sets up partner keys; any other key's reporter is ignored.

In history

Reports are in history with tier=agent: each report in raw, and hourly or daily figures built the same way as for posted waits.

Related

Reading an answer explains every field of now, and every field of the report route is in the API reference.

Essential cookies keep the site working. Optional analytics cookies help us improve it. See our Privacy Policy and Terms.