Can an AI agent book you a restaurant table?

28 of the 84 agents in this directory say they book things. 18 public posts record one actually doing it, and one of those posts is somebody getting banned.

Restaurant reservations are where the agent idea meets a system that was not built for it, and the collision has already happened once on this site's record.

What is being proposed

In his first long interview on 28 September 2026, Instinct's founder describes reservations as a system he intends to rebuild. The first half is brute force: rather than a person refreshing one restaurant's page, "you can theoretically just have the agent check every 5 seconds", across every restaurant in every major city.

The second half is the interesting one. He describes a two-sided match. The user wants a table for something that matters, a birthday or an anniversary or a friend in town. The restaurant, he argues, wants those bookings rather than "the local who keeps taking up a table once a night".

So the agent tells the restaurant what the occasion is, the restaurant prioritises on it, and both sides do better than first come first served. He says partnerships are coming, and that this is being rebuilt in one category because it matters to users.

It has already been tried, and it did not go well

On 6 September 2026, three weeks before that interview, a user's Resy account was deactivated and all of his future reservations cancelled. He asked his agent what it had been doing. It reported "roughly 200 API requests per hour, around the clock", checking availability.

That is the check-every-five-seconds strategy, running for one person, against one platform, and the platform's answer was to remove him. Not the agent. Him.

The other recorded attempts are less dramatic and point the same way. One agent spent seven minutes trying to book a restaurant that had closed two years earlier. Another was given the same job as a rival and only one of them finished it.

The occasion box already exists, and nobody checks it

The part of the proposal that sounds new is not. OpenTable already carries occasion tags for a birthday, an anniversary, a date or a business meal, with a notes field beside them. Resy already routes occasion tags into a guest profile the restaurant keeps between visits.

So the field is there, and it has always been unverified. Nobody at the restaurant asks for a birth certificate. That has been fine because the payoff was small: a written card, a candle in a dessert, a little more care over which table you get. Lying about it was possible and slightly shameful and mostly not worth it.

What the proposal changes is the payoff. If the occasion decides who gets the table, rather than what arrives with the pudding, the claim is worth money.

And an agent can make that claim instantly, in every restaurant in a city, without the small human friction of typing a lie about your own mother's birthday.

A signal that is unverified survives as long as claiming it costs something. Automate the claiming and attach a scarce table to the outcome, and the box stops carrying information. Everyone's dinner becomes an anniversary.

There is already a law about this

New York has legislated in this area. The Restaurant Reservation Anti-Piracy Act, signed in December 2024, requires a third-party reservation service to have a written agreement with the restaurant before it lists or arranges that restaurant's tables, and carries a civil penalty of up to $1,000 a day. It was written to kill the resale market, where people were selling hard-to-get tables, and OpenTable and Resy both supported it.

The bit that matters here is the shape of the rule rather than its target. It draws the line at a third party arranging a reservation without the restaurant's agreement. An agent booking on your behalf is not selling anything, so the resale part does not bite. Whether it is a third-party reservation service is a question nobody has answered, and at least one resale platform has already said it will relaunch in New York behind an AI chat interface and find out.

That is the honest state of it: a rule exists, it was aimed at something adjacent, and the first product to test the edge will decide what it means.

What this directory can tell you today

28 listings say they can book. What almost none of them publish is the part that matters for this: what their agent does when a table is not available, how often it checks, and whether the platform on the other side has agreed to any of it. Not one listing here names a reservation platform as a partner.

18 of 84 say anywhere public when the agent stops to ask you first. If an agent is going to describe your evening to a restaurant in order to get you seated, whether it checks that description with you is not a small detail.

What to watch

Whether any listing publishes a reservation partnership, which would be the first time one of these products has the written agreement New York's rule describes.

And whether a second user reports an account being closed. One is an argument between a platform and a customer. Two is a policy, and the person who pays for it is the one whose reservations get cancelled.