{ "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 Resy's 10.3 (F), and leads in every scored category.", "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": "Eat App (EAT APPLICATION DMCC)", "b": "Resy (American Express)", "name": "Vendor" }, { "a": "https://api.eatapp.co/partners/v2", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "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. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock", "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": "no document linked", "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": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Eat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category.", "question": "Which is better for AI agents, Eat App Partner API or Resy?" }, { "answer": "Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for Resy.", "question": "Can an agent call Eat App Partner API and Resy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 78 against 25", "Schema \u0026 documentation, 59 against 0", "Agent ergonomics, 66 against 0", "Security \u0026 auth, 43 against 3", "Payments \u0026 pricing, 15 against 0", "Maintenance \u0026 community, 40 against 25", "Transparency \u0026 trust, 52 against 30" ], "also": [ "A hosted endpoint, with nothing to install" ], "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": "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.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-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-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/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/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/resy-vs-square-appointments.json", "title": "Resy vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/resy-vs-square-appointments" } ], "scores": [ { "by": 53, "eat-app": 78, "edge": "eat-app", "key": "reliability", "name": "Reliability", "resy": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 59, "eat-app": 59, "edge": "eat-app", "key": "schema", "name": "Schema \u0026 documentation", "resy": 0, "weight": 13 }, { "by": 66, "eat-app": 66, "edge": "eat-app", "key": "ergonomics", "name": "Agent ergonomics", "resy": 0, "weight": 13 }, { "by": 40, "eat-app": 43, "edge": "eat-app", "key": "security", "name": "Security \u0026 auth", "resy": 3, "weight": 14 }, { "by": 15, "eat-app": 15, "edge": "eat-app", "key": "payments", "name": "Payments \u0026 pricing", "resy": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "eat-app": 40, "edge": "eat-app", "key": "maintenance", "name": "Maintenance \u0026 community", "resy": 25, "weight": 7 }, { "by": 22, "eat-app": 52, "edge": "eat-app", "key": "transparency", "name": "Transparency \u0026 trust", "resy": 30, "weight": 7 } ], "summary": "Eat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category. 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.", "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/eat-app-vs-resy", "json": "https://www.anchorterminal.com/compare/eat-app-vs-resy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-app-vs-resy.md", "slim": "https://www.anchorterminal.com/compare/eat-app-vs-resy.min.md" }, "markdown": "Eat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category. 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- 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### 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 25\n- Schema \u0026 documentation, 59 against 0\n- Agent ergonomics, 66 against 0\n- Security \u0026 auth, 43 against 3\n- Payments \u0026 pricing, 15 against 0\n- Maintenance \u0026 community, 40 against 25\n- Transparency \u0026 trust, 52 against 30\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\n\n### Resy (F)\n\nGood for: Diners booking in person through the app.\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 | Eat App Partner API | Resy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 25 | Eat App Partner API +53 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 0 | Eat App Partner API +59 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 0 | Eat App Partner API +66 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 3 | Eat App Partner API +40 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 0 | Eat App Partner API +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 25 | Eat App Partner API +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 30 | Eat App Partner API +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53.4 · D** | **10.3 · F** | |\n\n## Facts side by side\n\n| Fact | Eat App Partner API | Resy |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | Eat App (EAT APPLICATION DMCC) | Resy (American Express) |\n| Hosted endpoint | `https://api.eatapp.co/partners/v2` | no (local only) |\n| Transports | HTTP | |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock |\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 | no document linked |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\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**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### 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### 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, Eat App Partner API or Resy?\n\nEat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category.\n\n### Can an agent call Eat App Partner API and Resy without installing anything?\n\nEat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for Resy.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-app-vs-resy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-app-vs-resy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-app\", \"b\": \"resy\"}`. From a terminal: `anchor compare eat-app resy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-app.json and https://www.anchorterminal.com/api/v1/tools/resy.json\n\n## Other comparisons with Eat App Partner API or Resy\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.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 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- [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- [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- [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": "Eat App Partner API vs Resy", "url": "" } ], "description": "Eat App Partner scores 53.4 (D) to Resy's 10.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat App Partner API D 53.4", "Resy F 10.3", "scores" ], "h1": "Eat App Partner API vs Resy", "image": "https://www.anchorterminal.com/assets/og/compare-eat-app-vs-resy.png", "path": "/compare/eat-app-vs-resy", "published": "2026-10-01", "section": "tools", "title": "Eat App Partner vs Resy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/eat-app-vs-resy" }, "tokens": { "markdown": 2000, "slim": 680 }, "version": 1 }