Yes they all do work. I need them to exist so that I can pull the relevant data from the url client side for geolocation (in the case of lat/lng) and autocomplete (in the case of neighborhood/location) so that I can set the browse page with whatever was selected. These are not API since they do not return data, but rather should be under the browse path because they change the default state of the browse page. This seemed like the simplest way to get the data I need, and has the added benefit of letting django parse out anything nasty in the url.