{ "data": { "a": { "slug": "opentable", "name": "OpenTable APIs", "vendor": "OpenTable", "vendorUrl": "https://www.opentable.com", "kind": "http-api", "category": "local-bookings", "summary": "OpenTable's partner APIs let approved partners search restaurant availability and make, change and cancel reservations, for diners through the Consumer API or for restaurants' voice agents through the In-House Booking API, with OAuth 2.0 client credentials.", "url": "https://www.anchorterminal.com/tools/opentable", "markdownUrl": "https://www.anchorterminal.com/tools/opentable.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opentable.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opentable.json", "license": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "transports": [ "http" ], "remoteUrl": "https://platform.opentable.com", "packages": [], "auth": "oauth", "authNotes": "Partner approval required. A partner applies through OpenTable's become-a-partner form, the partnerships team reviews the application, and approved partners receive sandbox credentials and restaurant IDs in a welcome email. Tokens come from the OAuth 2.0 client credentials grant at https://oauth-pp.opentable.com (sandbox) or https://oauth.opentable.com (production), with the client ID and secret Base64-encoded in the Authorization header. The Platform Policy forbids sharing credentials and says OpenTable may require rotation. Restaurants connect a partner through an OAuth or unique-identifier onboarding flow in the Integrations Marketplace.", "pricing": "byo-plan", "pricingNotes": "No API prices are published. Use is governed by each partner's agreement with OpenTable, and the docs say new implementations may need additional contracting and certification. A sandbox is granted after approval. The change log describes a configurable OpenTable Service Fee (shown to diners as 2 per cent) that restaurants may pass on to diners on experiences, deposits and card holds (https://docs.opentable.com/).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the public API documentation (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.opentable.com", "capabilities": [ "booking.availability", "booking.reservations", "booking.venue", "crm.records" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "oauth", "webhooks", "sandbox", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 38.6, "grade": "E", "agentReady": false, "rank": 994, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 5, "payments": 5, "reliability": 35, "schema": 61, "security": 33, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.", "bestFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.", "strengths": [ "Diner-side Consumer API v2 and venue-side In-House Booking API both cover availability, slot lock, booking, change and cancellation", "Booking and cancellation policy endpoints return deposits, holds and cut-off rules before a booking is made", "X-Request-Id on POST, PUT and PATCH requests makes retries safe", "Error tables name business-rule failures such as DinerHasOverlappingReservations with their HTTP codes", "A sandbox environment with its own OAuth host is granted after approval" ], "weaknesses": [ "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials", "Rate limits are not published and come from the OpenTable representative", "No OpenAPI file, llms.txt or SDK, only a Postman collection", "The change log has one dated entry, the TLS 1.3 notice of 6 October 2025", "The Platform Policy allows API changes and suspension with or without notice and promises no support" ], "agentNotes": [ "Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes", "Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated", "Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner", "Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel", "Ask the OpenTable representative for the rate limit of each endpoint before going live" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 38.6 } ], "editorialScores": { "ergonomics": 69, "maintenance": 5, "payments": 5, "reliability": 35, "schema": 61, "security": 33, "transparency": 20 }, "provenanceScore": 64 }, "connect": { "http": "curl \"https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials\" -H \"Authorization: Basic BASE64_CLIENT_ID_AND_SECRET\"" }, "letme": { "capability": "https://letme.dev/booking.availability", "tool": "https://letme.dev/opentable" }, "area": "everyday", "provenance": { "legalEntity": "", "domain": "opentable.com", "domainRegistered": "1999-01-17", "endpointOnVendorDomain": true, "terms": "https://www.opentable.com/legal/terms-and-conditions", "privacy": "https://www.opentable.com/legal/privacy-policy", "statusPage": "https://status.opentable.com", "changelog": "https://docs.opentable.com/", "securityTxt": "unknown", "checked": "2026-10-14", "notes": [ "The terms and privacy URLs are the ones the API documentation links. www.opentable.com timed out on every request from our network on 14 October 2026, including robots.txt, so neither page nor the legal entity was read.", "The API's own Platform Policy (last updated 20 December 2024) is published at the top of docs.opentable.com and refers to each partner's agreement with OpenTable.", "status.opentable.com is a StatusDashboard page whose components and history load by script and were not readable to our reader.", "The change log is a section of the documentation (API Reference, Change Log), not a separate page.", "security.txt could not be fetched because www.opentable.com did not answer.", "RDAP gives opentable.com a registration date of 1999-01-17." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/opentable.json", "live": { "slug": "opentable", "probe": { "target": "https://platform.opentable.com", "method": "get", "lastAt": "2026-10-14T09:42:01.177574691Z", "lastOk": true, "lastStatus": 200, "lastMs": 476, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 545, "p95ms24h": 2988, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.opentable.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:44.535821064Z" }, "updatedAt": "2026-10-14T09:42:01.177574691Z" } }, "answer": "OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance \u0026 community.", "b": { "slug": "resy", "name": "Resy", "vendor": "Resy (American Express)", "vendorUrl": "https://resy.com", "kind": "platform", "category": "local-bookings", "summary": "Resy is American Express's restaurant reservation app and website for diners, with Resy OS for venues. Since 11 August 2026 it also lists Tock's restaurants, wineries and experiences, over 25,000 venues in all.", "url": "https://www.anchorterminal.com/tools/resy", "markdownUrl": "https://www.anchorterminal.com/tools/resy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/resy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/resy.json", "license": "Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock", "transports": [], "packages": [], "auth": "oauth", "authNotes": "No public agent access. An MCP endpoint at https://apigw.americanexpress.com/dining/v1/mcp answers 401 and publishes OAuth metadata with one scope, 600003928_DINING_RESY_MCP_APPS. Its authorisation server supports only client_secret_jwt client authentication and lists no registration endpoint, so only clients American Express has registered can connect. No public documentation for it was found.", "pricing": "paid", "pricingNotes": "No prices for venues or for API access were found on resy.com/join, which asks venues to book a demo. Diner pricing could not be read, because resy.com renders by script.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on resy.com/join or the MCP endpoint's OAuth metadata (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "capabilities": [ "booking.reservations", "booking.availability", "booking.venue" ], "tags": [ "not-for-agents", "sales-led", "hosted", "closed-source", "partner-only", "ios", "android", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 10.3, "grade": "F", "agentReady": false, "rank": 1068, "ranked": true, "rankOf": 1076, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 25, "payments": 0, "reliability": 25, "schema": 0, "security": 3, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-14" }, "negative": 0, "verdict": "Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.", "bestFor": "Diners booking in person through the app.", "strengths": [ "Over 25,000 venues after Tock's restaurants, wineries and experiences joined on 11 August 2026", "Deposits, prepayment, card holds and verified bookings are available to venues, per the platform security page", "A dated product change in the last 90 days" ], "weaknesses": [ "No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients", "Resy's terms, privacy policy and status page render by script and could not be read", "No published prices for venues or partners", "Resy describes blocking bots and brokers at scale, so automated booking through the website is unwelcome" ], "agentNotes": [ "Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP", "Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 10.3 } ], "editorialScores": { "ergonomics": 0, "maintenance": 25, "payments": 0, "reliability": 25, "schema": 0, "security": 3, "transparency": 8 }, "provenanceScore": 52 }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/resy" }, "area": "everyday", "provenance": { "legalEntity": "Resy Network, Inc.", "domain": "resy.com", "domainRegistered": "2001-11-14", "endpointOnVendorDomain": false, "terms": "", "privacy": "https://resy.com/privacy", "statusPage": "https://status.resy.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "resy.com renders every path, including /privacy, /terms and /.well-known/security.txt, as the same script-driven page, so the privacy policy, terms and any security.txt were not read. The privacy URL is the one the business site's footer links.", "The business site's footer reads Resy Network, Inc. and links separate Resy and Tock privacy policies and merchant terms.", "status.resy.com loads by script and showed no components or history to our reader.", "The MCP endpoint sits on americanexpress.com, not resy.com.", "RDAP gives resy.com a registration date of 2001-11-14." ], "score": 52 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/resy.json", "live": { "slug": "resy", "vendorStatus": { "page": "https://status.resy.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:51.941824987Z" }, "updatedAt": "2026-10-14T08:53:51.941824987Z" } }, "facts": [ { "a": "HTTP API", "b": "Platform", "name": "Kind" }, { "a": "OpenTable", "b": "Resy (American Express)", "name": "Vendor" }, { "a": "https://platform.opentable.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Your plan", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "b": "Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "couldn't be read", "b": "no document linked", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance \u0026 community.", "question": "Which is better for AI agents, OpenTable APIs or Resy?" }, { "answer": "OpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Resy.", "question": "Can an agent call OpenTable APIs and Resy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 35 against 25", "Schema \u0026 documentation, 61 against 0", "Agent ergonomics, 69 against 0", "Security \u0026 auth, 33 against 3", "Payments \u0026 pricing, 5 against 0", "Transparency \u0026 trust, 42 against 30" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.", "slug": "opentable", "watchFor": "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials" }, { "aheadOn": [ "Maintenance \u0026 community, 25 against 5" ], "also": null, "goodFor": "Diners booking in person through the app.", "slug": "resy", "watchFor": "No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients" } ], "job": { "capability": "booking.availability", "name": "Booking availability" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-opentable.json", "title": "Chope vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/chope-vs-opentable" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-resy.json", "title": "Chope vs Resy", "url": "https://www.anchorterminal.com/compare/chope-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.json", "title": "Eat App Partner API vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-resy.json", "title": "Eat App Partner API vs Resy", "url": "https://www.anchorterminal.com/compare/eat-app-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-tock.json", "title": "OpenTable APIs vs Tock", "url": "https://www.anchorterminal.com/compare/opentable-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-sevenrooms.json", "title": "Resy vs SevenRooms", "url": "https://www.anchorterminal.com/compare/resy-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-tablecheck.json", "title": "Resy vs TableCheck API", "url": "https://www.anchorterminal.com/compare/resy-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-thefork.json", "title": "Resy vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/resy-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-tock.json", "title": "Resy vs Tock", "url": "https://www.anchorterminal.com/compare/resy-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.json", "title": "OpenTable APIs vs SevenRooms", "url": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments.json", "title": "OpenTable APIs vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck.json", "title": "OpenTable APIs vs TableCheck API", "url": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-thefork.json", "title": "OpenTable APIs vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/opentable-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-square-appointments.json", "title": "Resy vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/resy-vs-square-appointments" } ], "scores": [ { "by": 10, "edge": "opentable", "key": "reliability", "name": "Reliability", "opentable": 35, "resy": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 61, "edge": "opentable", "key": "schema", "name": "Schema \u0026 documentation", "opentable": 61, "resy": 0, "weight": 13 }, { "by": 69, "edge": "opentable", "key": "ergonomics", "name": "Agent ergonomics", "opentable": 69, "resy": 0, "weight": 13 }, { "by": 30, "edge": "opentable", "key": "security", "name": "Security \u0026 auth", "opentable": 33, "resy": 3, "weight": 14 }, { "by": 5, "edge": "opentable", "key": "payments", "name": "Payments \u0026 pricing", "opentable": 5, "resy": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edge": "resy", "key": "maintenance", "name": "Maintenance \u0026 community", "opentable": 5, "resy": 25, "weight": 7 }, { "by": 12, "edge": "opentable", "key": "transparency", "name": "Transparency \u0026 trust", "opentable": 42, "resy": 30, "weight": 7 } ], "summary": "OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance \u0026 community. Both do booking availability.", "verdicts": { "opentable": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.", "resy": "Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/opentable-vs-resy", "json": "https://www.anchorterminal.com/compare/opentable-vs-resy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/opentable-vs-resy.md", "slim": "https://www.anchorterminal.com/compare/opentable-vs-resy.min.md" }, "markdown": "OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance \u0026 community. Both do booking availability.\n\n- OpenTable APIs: grade E, 38.6/100, rank #994 of 1076. Markdown https://www.anchorterminal.com/tools/opentable.md · JSON https://www.anchorterminal.com/api/v1/tools/opentable.json\n- Resy: grade F, 10.3/100, rank #1068 of 1076. Markdown https://www.anchorterminal.com/tools/resy.md · JSON https://www.anchorterminal.com/api/v1/tools/resy.json\n- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md\n- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md\n\n## Which one, for what\n\n### OpenTable APIs (E)\n\nGood for: Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.\n\nAhead on:\n- Reliability, 35 against 25\n- Schema \u0026 documentation, 61 against 0\n- Agent ergonomics, 69 against 0\n- Security \u0026 auth, 33 against 3\n- Payments \u0026 pricing, 5 against 0\n- Transparency \u0026 trust, 42 against 30\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials\n\n### Resy (F)\n\nGood for: Diners booking in person through the app.\n\nAhead on:\n- Maintenance \u0026 community, 25 against 5\n\nWatch for: No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients\n\n\n## Score by category\n\n| Category | Weight | OpenTable APIs | Resy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 25 | OpenTable APIs +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 0 | OpenTable APIs +61 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 0 | OpenTable APIs +69 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 3 | OpenTable APIs +30 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 0 | OpenTable APIs +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 5 | 25 | Resy +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 42 | 30 | OpenTable APIs +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.6 · E** | **10.3 · F** | |\n\n## Facts side by side\n\n| Fact | OpenTable APIs | Resy |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | OpenTable | Resy (American Express) |\n| Hosted endpoint | `https://platform.opentable.com` | no (local only) |\n| Transports | HTTP | |\n| Auth | OAuth | OAuth |\n| Pricing | Your plan | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Terms last updated | couldn't be read | no document linked |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | |\n| Terms restrict automated access | couldn't be read | |\n| Terms restrict benchmarking | couldn't be read | |\n| Terms or service can change without notice | couldn't be read | |\n| Arbitration or class-action waiver | couldn't be read | |\n\n## Verdicts\n\n**OpenTable APIs.** The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.\n\n**Resy.** Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.\n\n## Before you call either\n\n### OpenTable APIs\n\n1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes\n2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated\n3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner\n4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel\n5. Ask the OpenTable representative for the rate limit of each endpoint before going live\n\n### Resy\n\n1. Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP\n2. Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking\n\n## Questions\n\n### Which is better for AI agents, OpenTable APIs or Resy?\n\nOpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance \u0026 community.\n\n### Can an agent call OpenTable APIs and Resy without installing anything?\n\nOpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Resy.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/opentable-vs-resy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/opentable-vs-resy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"opentable\", \"b\": \"resy\"}`. From a terminal: `anchor compare opentable resy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/opentable.json and https://www.anchorterminal.com/api/v1/tools/resy.json\n\n## Other comparisons with OpenTable APIs or Resy\n\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Chope vs Resy](https://www.anchorterminal.com/compare/chope-vs-resy.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md)\n- [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md)\n- [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)\n- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)\n- [Resy vs Tock](https://www.anchorterminal.com/compare/resy-vs-tock.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md)\n- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md)\n- [OpenTable APIs vs TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md)\n- [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md)\n- [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-vs-square-appointments.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "OpenTable APIs vs Resy", "url": "" } ], "description": "OpenTable scores 38.6 (E) to Resy's 10.3 (F) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "OpenTable APIs E 38.6", "Resy F 10.3", "scores" ], "h1": "OpenTable APIs vs Resy", "image": "https://www.anchorterminal.com/assets/og/compare-opentable-vs-resy.png", "path": "/compare/opentable-vs-resy", "published": "2026-10-01", "section": "tools", "title": "OpenTable vs Resy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/opentable-vs-resy" }, "tokens": { "markdown": 2000, "slim": 630 }, "version": 1 }