{ "data": { "a": { "slug": "eat-app", "name": "Eat App Partner API", "vendor": "Eat App (EAT APPLICATION DMCC)", "vendorUrl": "https://restaurant.eatapp.co", "kind": "http-api", "category": "local-bookings", "summary": "Eat App is a restaurant reservation and table management system. Its Partner API lets booking channels check availability and create, change and cancel reservations, a Concierge API serves restaurant groups, and a read-only Restaurant MCP server connects AI assistants.", "url": "https://www.anchorterminal.com/tools/eat-app", "markdownUrl": "https://www.anchorterminal.com/tools/eat-app.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/eat-app.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/eat-app.json", "license": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements", "transports": [ "http" ], "remoteUrl": "https://api.eatapp.co/partners/v2", "packages": [], "auth": "mixed", "authNotes": "Partner approval required for the Partner API. A booking channel asks to become a partner (info@eatapp.co), Eat App activates partnerships restaurant by restaurant, and its support team issues a long-term API key sent as a Bearer token. A login endpoint also exchanges the partner's email and password for a 24-hour token. Concierge API keys are created by Eat App for restaurant groups. The Restaurant MCP server uses OAuth with dynamic client registration, PKCE and a single `mcp` scope, and the restaurant signs in with its Eat App login.", "pricing": "paid", "pricingNotes": "No per-call price. The pricing page marks API access in the Enterprise column only (Let's talk) and lists API and webhooks access as an add-on. Table management plans are $99, $199 and $389 a month, or $69, $159 and $299 billed yearly, with a 14-day trial and a $0 plan limited to 100 guests a month. The Restaurant MCP needs an active table management subscription. A sandbox host (api.eat-sandbox.co) is given to partners (https://restaurant.eatapp.co/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Partner or Concierge API docs, the MCP guide or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "mcp", "oauth", "sandbox", "status-page", "webhooks", "restaurants" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 53.4, "grade": "D", "agentReady": false, "rank": 752, "ranked": true, "rankOf": 1076, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.", "bestFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "strengths": [ "idempotency_token on Create Reservation returns the first success for a repeated request", "60 requests a minute stated, with a documented 429 body", "Better Stack status page with separate Partner API and Concierge API components and incident history", "Dated API changelog, latest entry 13 October 2026", "Restaurant MCP server with OAuth dynamic client registration and read-only access" ], "weaknesses": [ "A booking channel can book only at restaurants whose partnership Eat App has activated", "API access sits in the Enterprise column of the pricing page, priced through sales", "No OpenAPI file, llms.txt or SDK, only Postman collections", "A login endpoint accepts the partner's email and password for a 24-hour token", "No security.txt, and the trust centre content did not load for our reader" ], "agentNotes": [ "Send a unique idempotency_token with each new booking so a retry returns the first result", "Use POST /partners/v2/availability/range, not the legacy availability endpoint", "Keep include_tables ranges to 24 hours or less and pass covers with it", "Stay under 60 requests a minute and wait for the next minute after a 429", "Cancel by PATCH with status canceled, after which the reservation can no longer change" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 32 }, "provenanceScore": 71 }, "connect": { "http": "curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/eat-app" }, "area": "everyday", "provenance": { "legalEntity": "EAT APPLICATION DMCC", "domain": "eatapp.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://restaurant.eatapp.co/terms", "privacy": "https://restaurant.eatapp.co/privacy", "statusPage": "https://status.eatapp.co", "changelog": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of service (effective 10 September 2025) are entered into by EAT APPLICATION DMCC, Jumeirah Lake Towers, Dubai, licence DMCC-164040, and say the agreement also includes one executed with its licensee Swiggy Limited.", "The privacy policy names EAT APPLICATION DMCC and covers GDPR rights and a retention statement without fixed periods.", "The API changelog is a section of the Partner API Postman documentation.", "security.txt returns 404 on eatapp.co, restaurant.eatapp.co and api.eatapp.co. A trust centre at trust.eatapp.co loads by script and showed only its title to our reader.", "RDAP for eatapp.co did not answer, so the registration date is not recorded." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/eat-app.json", "live": { "slug": "eat-app", "probe": { "target": "https://api.eatapp.co/partners/v2", "method": "get", "lastAt": "2026-10-14T09:41:49.444870422Z", "lastOk": true, "lastStatus": 404, "lastMs": 157, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 175, "p95ms24h": 322, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.eatapp.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:05.16851429Z" }, "updatedAt": "2026-10-14T09:41:49.444870422Z" } }, "answer": "Eat App Partner API scores 53.4 (D) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 5 of 7 scored categories.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat App (EAT APPLICATION DMCC)", "b": "OpenTable", "name": "Vendor" }, { "a": "https://api.eatapp.co/partners/v2", "b": "https://platform.opentable.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements", "b": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-13", "b": "none", "name": "Last release" }, { "a": "2025-09-10", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Eat App Partner API scores 53.4 (D) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Eat App Partner API or OpenTable APIs?" }, { "answer": "Eat App Partner API takes an API key or an OAuth sign-in. OpenTable APIs uses an OAuth sign-in.", "question": "Do Eat App Partner API and OpenTable APIs need an API key?" }, { "answer": "Yes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and OpenTable APIs at https://platform.opentable.com.", "question": "Can an agent call Eat App Partner API and OpenTable APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 78 against 35", "Security \u0026 auth, 43 against 33", "Payments \u0026 pricing, 15 against 5", "Maintenance \u0026 community, 40 against 5", "Transparency \u0026 trust, 52 against 42" ], "also": null, "goodFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "slug": "eat-app", "watchFor": "A booking channel can book only at restaurants whose partnership Eat App has activated" }, { "aheadOn": null, "also": null, "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" } ], "job": { "capability": "booking.reservations", "name": "Restaurant reservations" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-eat-app.json", "title": "Chope vs Eat App Partner API", "url": "https://www.anchorterminal.com/compare/chope-vs-eat-app" }, { "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/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/eat-app-vs-sevenrooms.json", "title": "Eat App Partner API vs SevenRooms", "url": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json", "title": "Eat App Partner API vs TableCheck API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-thefork.json", "title": "Eat App Partner API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-tock.json", "title": "Eat App Partner API vs Tock", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tock" }, { "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/eat-app-vs-square-appointments.json", "title": "Eat App Partner API vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-resy.json", "title": "OpenTable APIs vs Resy", "url": "https://www.anchorterminal.com/compare/opentable-vs-resy" }, { "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" } ], "scores": [ { "by": 43, "eat-app": 78, "edge": "eat-app", "key": "reliability", "name": "Reliability", "opentable": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "eat-app": 59, "edge": "opentable", "key": "schema", "name": "Schema \u0026 documentation", "opentable": 61, "weight": 13 }, { "by": 3, "eat-app": 66, "edge": "opentable", "key": "ergonomics", "name": "Agent ergonomics", "opentable": 69, "weight": 13 }, { "by": 10, "eat-app": 43, "edge": "eat-app", "key": "security", "name": "Security \u0026 auth", "opentable": 33, "weight": 14 }, { "by": 10, "eat-app": 15, "edge": "eat-app", "key": "payments", "name": "Payments \u0026 pricing", "opentable": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 35, "eat-app": 40, "edge": "eat-app", "key": "maintenance", "name": "Maintenance \u0026 community", "opentable": 5, "weight": 7 }, { "by": 10, "eat-app": 52, "edge": "eat-app", "key": "transparency", "name": "Transparency \u0026 trust", "opentable": 42, "weight": 7 } ], "summary": "Eat App Partner API scores 53.4 (D) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 5 of 7 scored categories. Both do restaurant reservations.", "verdicts": { "eat-app": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/eat-app-vs-opentable", "json": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.md", "slim": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.min.md" }, "markdown": "Eat App Partner API scores 53.4 (D) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 5 of 7 scored categories. Both do restaurant reservations.\n\n- Eat App Partner API: grade D, 53.4/100, rank #752 of 1076. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json\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- 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### Eat App Partner API (D)\n\nGood for: Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.\n\nAhead on:\n- Reliability, 78 against 35\n- Security \u0026 auth, 43 against 33\n- Payments \u0026 pricing, 15 against 5\n- Maintenance \u0026 community, 40 against 5\n- Transparency \u0026 trust, 52 against 42\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\n\n### OpenTable APIs (E)\n\nGood for: Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.\n\nWatch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials\n\n\n## Score by category\n\n| Category | Weight | Eat App Partner API | OpenTable APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 35 | Eat App Partner API +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 61 | OpenTable APIs +2 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 69 | OpenTable APIs +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 33 | Eat App Partner API +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 5 | Eat App Partner API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 5 | Eat App Partner API +35 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 42 | Eat App Partner API +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53.4 · D** | **38.6 · E** | |\n\n## Facts side by side\n\n| Fact | Eat App Partner API | OpenTable APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat App (EAT APPLICATION DMCC) | OpenTable |\n| Hosted endpoint | `https://api.eatapp.co/partners/v2` | `https://platform.opentable.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Your plan |\n| x402 | no | no |\n| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation |\n| Read-only variant documented | yes | no |\n| llms.txt | no | no |\n| Last release | 2026-10-13 | none |\n| Terms last updated | 2025-09-10 | couldn't be read |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n\n## Verdicts\n\n**Eat App Partner API.** A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.\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## Before you call either\n\n### Eat App Partner API\n\n1. Send a unique idempotency_token with each new booking so a retry returns the first result\n2. Use POST /partners/v2/availability/range, not the legacy availability endpoint\n3. Keep include_tables ranges to 24 hours or less and pass covers with it\n4. Stay under 60 requests a minute and wait for the next minute after a 429\n5. Cancel by PATCH with status canceled, after which the reservation can no longer change\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## Questions\n\n### Which is better for AI agents, Eat App Partner API or OpenTable APIs?\n\nEat App Partner API scores 53.4 (D) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 5 of 7 scored categories.\n\n### Do Eat App Partner API and OpenTable APIs need an API key?\n\nEat App Partner API takes an API key or an OAuth sign-in. OpenTable APIs uses an OAuth sign-in.\n\n### Can an agent call Eat App Partner API and OpenTable APIs without installing anything?\n\nYes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and OpenTable APIs at https://platform.opentable.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-app-vs-opentable.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-app-vs-opentable.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-app\", \"b\": \"opentable\"}`. From a terminal: `anchor compare eat-app opentable`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-app.json and https://www.anchorterminal.com/api/v1/tools/opentable.json\n\n## Other comparisons with Eat App Partner API or OpenTable APIs\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [Eat App Partner API vs SevenRooms](https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.md)\n- [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md)\n- [Eat App Partner API vs TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Eat App Partner API vs Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.md)\n- [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md)\n- [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md)\n- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.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", "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": "Eat App Partner API vs OpenTable APIs", "url": "" } ], "description": "Eat App Partner scores 53.4 (D) to OpenTable's 38.6 (E) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat App Partner API D 53.4", "OpenTable APIs E 38.6", "scores" ], "h1": "Eat App Partner API vs OpenTable APIs", "image": "https://www.anchorterminal.com/assets/og/compare-eat-app-vs-opentable.png", "path": "/compare/eat-app-vs-opentable", "published": "2026-10-01", "section": "tools", "title": "Eat App Partner vs OpenTable for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable" }, "tokens": { "markdown": 2200, "slim": 730 }, "version": 1 }