Resy logo
x Hani

Resy’s biggest competitor isn’t OpenTable. It’s irrelevance.

AI assistants are already answering dining questions. Right now, without Resy. A diner asks ChatGPT where to eat in the West Village on a Tuesday night and gets an answer assembled from review sites, stale data, and guesswork. No real-time availability. No booking. No Resy.

That is not a gap. That is an open door. But open doors close. If AI assistants learn to answer dining questions without Resy's data, without Resy's inventory, availability, and booking flow, the product becomes optional in the moments that matter most.

The question is not whether Resy builds an agentic strategy. It is whether Resy leads this shift or chases it.

The Vision: Resy becomes the default dining intent layer across every AI interface by 2027, not by being on every platform, but by being the most reasonably structured, context-rich, and trustworthy restaurant data source any agent can call.

The dining landscape is being rewired

Consumer intent is moving off search boxes and into conversational, agentic interfaces. ChatGPT, Google Gemini, Meta AI, and a wave of voice-first assistants are now where dining decisions increasingly begin. This is not a future trend, it is happening now, at a scale the restaurant industry hasn't yet caught up to.

The critical dynamic: these interfaces don't return ten results. They return one answer. The platform that powers that answer wins the diner. The question is whether Resy is that platform or whether it isn't in the conversation at all.

1.2B

Monthly active users across generative AI assistants globally

MRFR market analysis, Q1 2025 · ChatGPT, Gemini, Meta AI, Copilot combined

52%

of US diners open to AI-powered restaurant recommendations based on past orders

DoorDash Delivery Trends Report, March 2025 · n=1,504 US consumers

60%

of Millennials, Resy's core demographic, open to AI dining recommendations

DoorDash Delivery Trends Report, March 2025 · highest of any generation surveyed

13.5%

of consumers already ask AI tools for restaurant and dining recommendations today

Attest Consumer AI Adoption Report, January 2025 · n=5,000 US, UK, CA, AU

The Non-Obvious Insight

The 13.5% who already use AI for dining recommendations is early-adopter behavior, but the 52% who say they are open to it signals the mass market is right behind. That gap between current behavior and stated openness is the window. It closes when a competitor occupies the position first and trust compounds around them. Resy's structural advantage, live inventory, behavioral signals, Amex cardholder context, is most valuable right now, before the default is set.

Where Discovery Happens Today

Google Maps, Yelp, social media

83% of diners begin restaurant discovery online, split between search engines and map apps. Resy has visibility in this world through SEO and app presence.

RightResponse AI Diner Survey, 2024 · n=1,000+ US diners

Where Discovery Is Moving

Conversational AI, voice, agentic surfaces

Intent is migrating into ChatGPT, Gemini, Apple Intelligence, and embedded AI in travel and calendar apps, surfaces where Resy has no guaranteed presence today.

Attest Consumer AI Report, Jan 2025 · DoorDash Trends Report, 2025

How Resy shows up in agentic channels

Three bets, ranked by leverage. Not every platform matters equally, the strategy is to win deeply in the highest-intent contexts first, then expand.

Bet 1 · Highest leverage

Native AI assistant integrations (ChatGPT Plugins, Gemini Actions, Apple Intelligence)

These are where dining intent is already expressing itself at scale. The UX pattern that wins: Resy surfaces as a direct booking action, not a search result. Diner says “book somewhere great in Tribeca tonight”, Resy returns a curated shortlist with availability, not a link to browse.

Bet 2 · Partnership multiplier

Amex ecosystem, card-linked agentic moments

Amex members using AI-assisted financial tools are the highest-value dining segment in the world. The integration here isn't a restaurant suggestion, it's a contextual dining recommendation at the moment of financial planning, travel booking, or concierge interaction.

Bet 3 · Platform foundation

Extensibility layer, MCP / agent framework compatibility

Build Resy as a first-class tool in the emerging agent-tool ecosystem (Model Context Protocol, LangChain, etc.) so any developer building a dining-adjacent agent defaults to Resy as their data and booking layer.

The quality bar

A Resy recommendation in an agentic context must be more reliable than a Google search result. Zero hallucinated availability. Zero stale data. If an agent surfaces a Resy booking and it fails, we lose the channel. The quality bar is: every agentic Resy interaction ends in a confirmed reservation or an honest “nothing available.”

Resy's inventory is the moat, if we build it right

Agents don't search, they reason. The restaurant that wins the agent's recommendation is not the most reviewed one on the internet. It is the one with the most complete, structured, and trustworthy data profile available at query time. Resy has the raw material. The work is making it machine-readable.

01

Structured inventory schema

A canonical data schema for every Resy restaurant: cuisine, vibe, occasion tags, price signal, neighborhood, dietary accommodations, ambiance. This becomes the vocabulary agents use to match diner intent to restaurant context.

02

Real-time availability API

Agents need sub-second, reliable availability signals. Rebuild the availability surface specifically for programmatic, high-frequency agentic queries, with semantic slots, rate tiers, and graceful degradation.

03

Behavioral signal layer

Resy holds booking signals no review platform has: actual reservation rates, return diner patterns, peak demand windows. Exposed safely, these make Resy's recommendations more accurate than anything scraped from Yelp.

04

Developer experience

Best-in-class SDKs, sandbox environments, and a developer community program. The goal: any developer building a dining agent integrates Resy first, in an afternoon, and never looks elsewhere.

Turning behavioral shifts into product bets

User attention has already moved. The question is what the new intent patterns demand from the product, and what bets we make now before they become obvious.

The shift

From search to delegation

Product Bet

Diners increasingly don't want to choose, they want to be chosen for. “Book me something good” is replacing “show me options.” Resy needs a strong personalization signal to be surfaced confidently by agents, not just passively returned as a list item. The agent needs to trust Resy's recommendation before the diner does.

The shift

From browsing to trust transfer

Product Bet

An agent recommending a single restaurant is a chain of trust: the diner trusts the agent, the agent trusts Resy's data. Every quality failure, stale hours, wrong availability, closed restaurant, breaks that chain permanently. Reliability of data is not a backend concern. It is the product's most important feature.

The shift

From category to context

Product Bet

AI-native intent is richer than keyword search. “Somewhere impressive for a work dinner with a vegetarian, not too loud” is a single query requiring occasion, dietary, social, and sensory parsing. Resy's inventory schema must encode context, not just cuisine type and price range, to surface accurately in these high-stakes moments.

The shift

From app to ambient

Product Bet

The highest-intent dining moments are migrating to voice, car, wearable, smart speaker, and into AI embedded in calendar and travel apps. A user planning a trip who says “find me a great dinner Thursday” is where Resy needs to be. Not as a notification. Not as an ad. As a reliable, contextual answer.

What we're actually competing on

In an agentic world the competitive map looks different. Resy is not competing on SEO or app-store ranking. It is competing on data quality, API reliability, and partnership depth. Here is the honest read.

OpenTable

Scale Google native

Larger global inventory, already embedded in Google Maps reservations. The structural gap: OpenTable's data schema is older and less rich, an advantage Resy can exploit where quality beats quantity.

Google / Maps

Distribution moat Gemini native

Partner and competitor simultaneously. The strategy is not to fight Google's distribution, it is to be the best booking layer Google's AI surfaces, not a restaurant listing competitor.

Yelp / Perplexity

Review depth Discovery signals

Strong on discovery content but structurally weak on real-time transactional data. Agents need availability and bookability, not review volume. Resy's transactional layer wins here.

Resy's unfair advantage

Amex cardholders Live inventory Behavioral signals

No competitor holds Amex's cardholder data, Resy's reservation signals, and a major card network's distribution simultaneously. This combination is unreplicable. That is the strategy.