Currently goplaces search and goplaces details return open_now but not businessStatus. The underlying Places API (New) already returns this field — it just isn't mapped to the output.
Suggestion: include businessStatus in both human-readable and --json output. Possible values:OPERATIONAL, CLOSED_TEMPORARILY, CLOSED_PERMANENTLY.
Why it matters:
When using goplaces in an agentic context (e.g. an AI assistant planning a visit and booking it to calendar), you want to know a place is still operating — not just whether it's open right now. open_now: false
is ambiguous: it could mean "closed for the night" or "closed forever". A separate status field makes this unambiguous without requiring a second API call.
Suggested output (human):
- Kafenion Amsterdam — Bloemgracht 49
Rating: 4.9 (3413) · Open now: yes · Status: OPERATIONAL
Suggested output (--json):
{ "name": "Kafenion Amsterdam", "business_status": "OPERATIONAL", ... }
The field is already available in the API response — this should be a small mapping change.
Currently
goplaces searchandgoplaces detailsreturnopen_nowbut notbusinessStatus. The underlying Places API (New) already returns this field — it just isn't mapped to the output.Suggestion: include
businessStatusin both human-readable and--jsonoutput. Possible values:OPERATIONAL, CLOSED_TEMPORARILY, CLOSED_PERMANENTLY.Why it matters:
When using goplaces in an agentic context (e.g. an AI assistant planning a visit and booking it to calendar), you want to know a place is still operating — not just whether it's open right now. open_now: false
is ambiguous: it could mean "closed for the night" or "closed forever". A separate status field makes this unambiguous without requiring a second API call.
Suggested output (human):
Rating: 4.9 (3413) · Open now: yes · Status: OPERATIONAL
Suggested output (--json):
{ "name": "Kafenion Amsterdam", "business_status": "OPERATIONAL", ... }The field is already available in the API response — this should be a small mapping change.