Mu now treats places lookup as a first-class service, sitting alongside search, weather, markets, and news in the agent’s toolset. When you ask “where is the nearest post office” or “what’s the address of that café”, the agent can call a dedicated places API instead of scraping a general search result. It’s the same pattern as the rest of Mu: a real service, exposed over MCP, charged per request, and available on your home screen if you’re signed in.
The agent can answer everyday location questions — where a business is, what’s nearby, or what a set of coordinates means. It works inline with the other tools, so you can ask “what’s the weather at that address” or “show me the news for that city” without switching context. The data comes from Google Places when you configure an API key, and from open data sources (like OpenStreetMap) otherwise. Coverage and accuracy depend on what you’ve set up. No single provider covers everything, and the agent will tell you when it can’t find a result.
This is part of the same philosophy: tools, not feeds. You pay for the lookups you use, there’s no tracking, and the agent doesn’t guess. If the open data says “no results”, it says so. If the Google key is missing, it falls back. You control what’s available. Places is a utility, like mail or search — nothing more, nothing less.