OpenTable — can an agent use it?
OpenTable has a comprehensive partner API (9 families including full booking lifecycle) and is one of the most AI-integrated reservation platforms — launch partner for OpenAI Operator, ChatGPT booking, 20+ voice AI partners. But every pathway is partner-gated: no self-serve API key, multi-week approval, negotiated pricing. The consumer ToS explicitly bans 'generative AI' and 'automated assistants' for unauthorized use, and robots.txt blocks all major AI crawlers by name. An agent can book a table through OpenTable — but only if OpenTable has already said yes.
FIND & RETRIEVE · 4.8
ACT & TRANSACT · 3.4
TRUST & DURABILITY · 4.8
FIND & RETRIEVE4.8/10Can an agent get correct information?
Machine-readable surface4.5/10
Comprehensive sitemap (102 sub-sitemaps covering restaurants, cuisines, landmarks, dining programs). Reserve with Google integration implies schema.org markup on restaurant pages. However, default robots.txt is Disallow: / for all agents, with Claude, ChatGPT, Perplexity and OAI-SearchBot explicitly blocked by name. No llms.txt, no .well-known/mcp.json. The homepage itself returns 403 to non-browser user-agents. Good underlying structure, actively walled off. source
Information retrieval quality5/10
Restaurant pricing for the platform is clearly published ($149–499/mo + per-cover fees). The partner API returns live availability, menu data, guest profiles, and reviews — current and specific. But API pricing is entirely opaque (negotiated per-partner). For a consumer-facing agent, basic restaurant information is accessible through Google's structured data integration, but direct retrieval from opentable.com is blocked by the 403/robots wall. source
Documentation for machines5/10
docs.opentable.com exists and returns 200, but requires partner authentication to view content. Third-party documentation (Vorp Labs, StayAPI, Hostie.ai) describes 9 API families with OAuth 2.0 auth, X-Request-Id idempotency, JSON format, and webhook support. Rate limits (~1,000 req/hr/restaurant) are mentioned but not precisely published per endpoint. The documentation is real and reportedly comprehensive — but invisible without a partner login. source
ACT & TRANSACT3.4/10Can an agent do the job?
Action coverage7/10
The partner API covers the full restaurant reservation lifecycle: availability checks, slot locking, reservation creation/modification/cancellation (Booking API), plus CRM, menus, POS, reviews, private dining, directory, sync, and profile content APIs. Webhooks for reservation events. Test mode (sandbox) mirrors production. Coverage is strong — an approved agent can do everything a human can do on the restaurant side. Score limited because consumer-side actions (diner search, booking as a guest) require being an approved consumer-facing partner. source
Agent protocol support2/10
No official MCP server. No .well-known/mcp.json. Not in the MCP registry. Five community-built MCP servers exist (chrischall/opentable, Apify, Bright Data, Strider Labs, clearpath/opentable-booker) but all rely on browser automation (Playwright) or scraping, violating OpenTable's ToS. OpenTable's AI integration strategy routes through formal partnerships (OpenAI Operator, ChatGPT, Google Spark), not open protocols. source
Access & auth friction3/10
No self-serve API key generation. Access requires a 5-step partner application (contact details, email/phone verification, organization details, product specifications), followed by a 3-4 week approval process. After approval: sandbox access, internal testing, QA review by OpenTable, then production deployment. OAuth 2.0 once in — but getting in is a gated commercial process, not a developer signup. source
Agent payment capability1.5/10
No support for ACP, AP2, MPP, or x402. Restaurants pay OpenTable via traditional subscription billing ($149–499/mo + per-cover fees). Diners pay the restaurant directly. No programmatic billing management or agent-initiated payment capability exists in the public or partner API documentation. source
Cost & rate fairness3.5/10
No public API pricing — all rates are negotiated per-partner. Rate limits approximately 1,000 requests/hour/restaurant with automatic throttling during peak hours, but exact limits vary by endpoint and are set per agreement. No free developer tier. Initial development may qualify for free sandbox access, but production deployment terms are opaque. The contrast with the clearly published restaurant subscription pricing ($149–499/mo) makes the API cost opacity conspicuous. source
TRUST & DURABILITY4.8/10Will it still work next quarter?
Permission & ToS stance3/10
Consumer ToS Section 13 explicitly prohibits 'any deep-link, robot, spider, scraper, generative AI or other AI technology including...automated assistants.' Section 4 restricts reservation abuse. robots.txt blocks all major AI crawlers by name (Claude-User, Claude-SearchBot, ChatGPT-User, OAI-SearchBot, PerplexityBot). Yet OpenTable simultaneously partners with OpenAI Operator, ChatGPT, Google Gemini/Spark, Microsoft Copilot, Perplexity, Alexa+, and 20+ voice AI platforms. The stance is two-tier: authorized partners welcome, everyone else legally excluded. source
Reliability & continuity6.5/10
Professional status page (status.opentable.com) with 15 monitored components across 4 groups including API-level monitoring (InHouse Booking API, Network Access API, Online Booking API, Restaurant Partner API). Currently all operational. ~22 tracked outages since August 2025. SOC 2 Type II certified, PCI compliant. No evidence of sudden API deprecations or pricing upheavals. OpenTable has been operational since 1998 under Booking Holdings since 2014 — long track record. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- opentable.com/robots.txt — robots.txt — default deny, explicit AI crawler blocks (accessed 2026-09-20)
- opentable.com/legal/terms-and-conditions — Consumer ToS — Section 13 bans generative AI and automated assistants (accessed 2026-09-20)
- opentable.com/restaurant-solutions/api-partners/bec… — Partner application — 5-step gated process, 3-4 week approval (accessed 2026-09-20)
- opentable.com/restaurant-solutions/api-partners/faqs — API partner FAQs — capabilities, sandbox, integration process (accessed 2026-09-20)
- docs.opentable.com — API documentation portal (partner-authenticated) (accessed 2026-09-20)
- status.opentable.com — Status page — 15 components, 4 groups, API-level monitoring (accessed 2026-09-20)
- vorplabs.com/agent-tools/opentable-cli — Agent tools assessment — 9 API families, OAuth 2.0, rate limits (accessed 2026-09-20)
- opentable.com/restaurant-solutions/resources/openai — OpenAI Operator launch partnership (accessed 2026-09-20)
- opentable.com/blog/press/page/summer-product-launch — Summer 2026 AI integrations — ChatGPT booking, 17x LLM-driven diners (accessed 2026-09-20)
- pulsemcp.com/servers/chrischall-opentable — Community MCP server — browser automation, violates ToS (accessed 2026-09-20)
- opentable.com/sitemap.xml — Sitemap index — 102 sub-sitemaps (accessed 2026-09-20)