Siri AI reached iPhones on 14 September, and a local recommendation is one of the three things Apple's own announcement says the assistant is for. The sentence runs: "Whether a user is looking for the score of a football game, tips for planning a vacation, or the best local coffee spot in a new city, Siri AI will leverage information from across the web to deliver helpful, accurate answers."
Apple picked the restaurant example itself
Two of those examples have obvious sources. A football score comes from a feed. Holiday tips come from the enormous quantity of travel writing already indexed. The coffee spot is the awkward one, because the answer has to be assembled from pages published by small businesses that had no idea they were writing for an assistant.
Apple went further down the same road in its list of app actions. Alongside texting in WhatsApp and playing a book on Audible, the announcement says that soon "users will be able to ask Siri AI to draft an email in Microsoft Outlook, search for a homework assignment in Notability, or add a restaurant recommendation to Tripsy." A restaurant turns up twice in Apple's launch material, both times as something the assistant fetches rather than something the user types.
Britain is inside the launch and the EU is not
Apple's statement on availability is short: "Siri AI will not be available initially in the EU on iOS, iPadOS, and watchOS." The June explanation was blunter about the cause. "Due to the Digital Markets Act (DMA), Apple will not be able to ship Siri AI in the European Union with the release of iOS 27 and iPadOS 27," Apple wrote, arguing that regulators would require it to "give any AI system nearly unlimited access to a user's device, as well as the ability to act on that access autonomously without a user's ongoing visibility and control." There is, Apple added, "currently no timeline" for changing that. macOS 27 and visionOS 27 are unaffected, and China is excluded separately while Apple works through a different set of regulatory requirements.
9to5Mac summarised the rest as "available worldwide, except in two key territories: the EU and China". Britain is in neither. Dublin sits outside this launch and Belfast sits inside it, with no end date attached to the gap.
The English requirement describes the current audience precisely
Siri AI, per 9to5Mac, "is only available for devices where the language is set to English" at launch, with French, Japanese, Korean, Portuguese and Spanish following next month. That is a condition on the handset rather than on the index, but it fixes who is asking. For the next few weeks, anyone putting a dining question to Siri AI is doing it on a phone set to English, which is the audience a British restaurant was already writing for.
The rollout is throttled at both ends
Access is not automatic. MacRumors reported that users join a waitlist through Settings by choosing "Try Siri AI (Beta)", and that "wait times seem to vary, with some users receiving access to Siri AI within a few minutes of signing up and others having to wait a few hours or even days." It also needs an iPhone 15 Pro or newer.
There is a cap at the other end. Apple's note says that "certain Apple Intelligence features that rely on server-side models are subject to daily usage limits, including but not limited to Siri AI". The assistant answering a question about dinner is metered, and the note gives no number.
Both throttles are temporary, and they point the same way. The volume of dining questions Siri AI fields in Britain this month is small. The volume it fields once the waitlist clears and the caps loosen is a different figure entirely, and nothing about the second number is contingent on anything a restaurant does.
What is contingent on the restaurant is the material the answer gets built from. The assistant reads what it can find at the moment the question arrives, and there is no step where it asks anyone to clarify. Whatever a restaurant has already published in a form a machine can parse is the whole of its contribution, and that work has to be done before the question is put, not after.