amadan
Visitor country from the edge, for apps to bias location search Feature Request open
Ask: pass the visitor's country (ISO 3166-1 alpha-2, as resolved from the client IP at the CARLOS edge) to the app on every request, e.g. a header the router signs or strips like the identity headers (X-Carlos-Viewer-Country), so apps never trust a client-supplied value.
Why (Tito, 2026-10-09): the buyer billing address search (server-side Google Places API (New), PRO-5485) returns worldwide results for "27 Frederick Street" — Birmingham, New Jersey, Australia — for an Irish school. Places can bias by regionCode / includedRegionCodes, but the app has no idea where the visitor is: the edge has the IP, the instance only sees the router. We'd rather not run our own GeoIP database in each app (per-app licence, updates, and it duplicates what the edge already knows).
Nice to have: region/subdivision and approximate lat/lng (city-level), for a locationBias circle. Country alone covers most of the value.
Tito will use it as a soft bias only (never to restrict or price anything), falling back to the event's venue/country when absent.