{ "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": 759, "ranked": true, "rankOf": 1094, "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-15T11:29:52.483674937Z", "lastOk": true, "lastStatus": 404, "lastMs": 145, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 159, "p95ms24h": 334, "samples24h": 254, "samples30d": 289, "days": [ { "date": "2026-10-14", "probes": 166, "ok": 166 }, { "date": "2026-10-15", "probes": 123, "ok": 123 } ] }, "vendorStatus": { "page": "https://status.eatapp.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-15T10:06:02.012989773Z" }, "securityTxt": { "url": "https://eatapp.co/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-14T15:46:10.968641635Z" }, "pages": [ { "url": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "kind": "changelog", "status": 200, "checkedAt": "2026-10-14T21:00:05.81208198Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://restaurant.eatapp.co/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-14T21:06:16.340363188Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2284dd604709" }, { "url": "https://restaurant.eatapp.co/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-14T21:06:18.542982745Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bd15b9f7f27f" }, { "url": "https://restaurant.eatapp.co/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-14T21:06:20.388265759Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "598d432d0014" } ], "updatedAt": "2026-10-15T11:29:52.483674937Z" } }, "answer": "TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "tablecheck", "name": "TableCheck API", "vendor": "TableCheck Inc.", "vendorUrl": "https://www.tablecheck.com", "kind": "http-api", "category": "local-bookings", "summary": "TableCheck is a restaurant reservation and guest management platform used mainly in Japan and Asia. Its API components cover availability, booking, CRM, POS and distribution to booking sites, with an MCP server for merchants.", "url": "https://www.anchorterminal.com/tools/tablecheck", "markdownUrl": "https://www.anchorterminal.com/tools/tablecheck.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tablecheck.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tablecheck.json", "license": "Proprietary service under the TableCheck API Terms of Service", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.tablecheck.com/api/", "packages": [], "auth": "api-key", "authNotes": "Sales-led. Email api@tablecheck.com, complete the API Portal questionnaire and accept the API terms. Each approved request gets one `secret_key` per environment in the `Authorization` header, limited to the approved components and, for aggregators, approved venues. The API team rolls keys on request. The MCP server needs the `mcp_merchant` component added to a key (https://tablecheck.atlassian.net/wiki/spaces/API/pages/44630975).", "pricing": "paid", "pricingNotes": "No public price. The access page says \"Fees may vary\" and pricing is given during the application. No free tier. Test accounts and test data are prepared on request (https://tablecheck.atlassian.net/wiki/spaces/API/pages/43909423, checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation or the OpenAPI files read (checked 2026-10-14).", "endpoints": [] }, "toolCount": 20, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://tablecheck.atlassian.net/wiki/spaces/API/overview", "openapi": "https://api.tablecheck.com/api/booking/v1/docs", "capabilities": [ "booking.availability", "booking.reservations", "booking.venue", "booking.orders" ], "tags": [ "hosted", "closed-source", "rest", "openapi", "mcp", "sales-led", "status-page", "diner-side", "venue-side" ], "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 666, "ranked": true, "rankOf": 1094, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.", "bestFor": "Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.", "strengths": [ "OpenAPI 3.0 YAML served for each component, with a written change and deprecation policy", "Separate APIs for diner-side platforms (Availability, Distribution, Web Booking) and venue-side systems (Booking, CRM, POS)", "MCP for Merchants hides guest names, phones and emails unless asked and supports read-only keys", "MCP write tools take an idempotency key and are annotated destructive", "Rate limit stated as 10,000 requests per 5 minutes per component" ], "weaknesses": [ "Access needs an emailed application, case-by-case approval and fees quoted privately", "MCP for Merchants is under development and its tools may change without a version bump", "REST POST /reservations has no idempotency key", "Keys are issued and rolled only by the API team, with no audit log found", "Booking v1 needs per-venue approval for aggregators, and only a production environment exists by default" ], "agentNotes": [ "Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue", "Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it", "Call `hold_table` (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes", "Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from `list_shops`", "Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 45 }, "provenanceScore": 86 }, "connect": { "claudeCode": "claude mcp add --transport http tablecheck \\\n https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1 \\\n --header \"Authorization: Bearer $TABLECHECK_API_KEY\"", "config": { "mcpServers": { "tablecheck": { "headers": { "Authorization": "Bearer ${TABLECHECK_API_KEY}" }, "type": "http", "url": "https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1" } } } }, "letme": { "capability": "https://letme.dev/booking.availability", "tool": "https://letme.dev/tablecheck" }, "area": "everyday", "provenance": { "legalEntity": "TableCheck Inc.", "domain": "tablecheck.com", "domainRegistered": "1998-07-01", "endpointOnVendorDomain": true, "terms": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service", "privacy": "https://www.tablecheck.com/en/policy/privacy", "statusPage": "https://tablecheck.statuspage.io", "changelog": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The API Terms of Service (enacted 10 December 2018) are with TableCheck, Inc. outside Mainland China and its designated entity inside it.", "The privacy policy (revised 14 September 2026) names TableCheck Inc., KR Ginza II 5F, 2-15-2 Ginza, Chuo-ku, Tokyo.", "The API documentation is hosted on tablecheck.atlassian.net. api.tablecheck.com redirects there.", "www.tablecheck.com/.well-known/security.txt returns an HTML page, read as no security.txt.", "RDAP gives a registration date of 1998-07-01 for tablecheck.com." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tablecheck.json", "live": { "slug": "tablecheck", "probe": { "target": "https://api.tablecheck.com/api/", "method": "get", "lastAt": "2026-10-15T11:30:12.848702865Z", "lastOk": true, "lastStatus": 200, "lastMs": 683, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 711, "p95ms24h": 766, "samples24h": 254, "samples30d": 289, "days": [ { "date": "2026-10-14", "probes": 166, "ok": 166 }, { "date": "2026-10-15", "probes": 123, "ok": 123 } ] }, "vendorStatus": { "page": "https://tablecheck.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-15T11:32:33.723558782Z" }, "securityTxt": { "url": "https://tablecheck.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-14T15:46:26.179117199Z" }, "pages": [ { "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889", "kind": "changelog", "status": 200, "checkedAt": "2026-10-14T21:08:24.547841382Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d5fcab81d8f1" }, { "url": "https://www.tablecheck.com/en/policy/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-14T21:17:56.562899241Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c4d046dd9e79" }, { "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service", "kind": "terms", "status": 200, "checkedAt": "2026-10-14T21:08:28.365867172Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "80e633567945" } ], "updatedAt": "2026-10-15T11:32:33.723558782Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat App (EAT APPLICATION DMCC)", "b": "TableCheck Inc.", "name": "Vendor" }, { "a": "https://api.eatapp.co/partners/v2", "b": "https://api.tablecheck.com/api/", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "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 under the TableCheck API Terms of Service", "name": "Licence" }, { "a": "none", "b": "20", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "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": "2022-10-11", "name": "Terms last updated" }, { "a": "no date given", "b": "2016-12-14", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Eat App Partner API or TableCheck API?" }, { "answer": "Eat App Partner API takes an API key or an OAuth sign-in. TableCheck API needs an API key.", "question": "Do Eat App Partner API and TableCheck API need an API key?" }, { "answer": "Yes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and TableCheck API at https://api.tablecheck.com/api/.", "question": "Can an agent call Eat App Partner API and TableCheck API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 15 against 0", "Maintenance \u0026 community, 40 against 35" ], "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": [ "Schema \u0026 documentation, 77 against 59", "Agent ergonomics, 72 against 66", "Transparency \u0026 trust, 66 against 52" ], "also": null, "goodFor": "Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.", "slug": "tablecheck", "watchFor": "Access needs an emailed application, case-by-case approval and fees quoted privately" } ], "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-tablecheck.json", "title": "Chope vs TableCheck API", "url": "https://www.anchorterminal.com/compare/chope-vs-tablecheck" }, { "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/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-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-tablecheck.json", "title": "Resy vs TableCheck API", "url": "https://www.anchorterminal.com/compare/resy-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/tablecheck-vs-tock.json", "title": "TableCheck API vs Tock", "url": "https://www.anchorterminal.com/compare/tablecheck-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-tablecheck.json", "title": "OpenTable APIs vs TableCheck API", "url": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.json", "title": "Square Appointments (Bookings API) vs TableCheck API", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork.json", "title": "TableCheck API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.json", "title": "SevenRooms vs TableCheck API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck" } ], "scores": [ { "by": 2, "eat-app": 78, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "tablecheck": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "eat-app": 59, "edge": "tablecheck", "key": "schema", "name": "Schema \u0026 documentation", "tablecheck": 77, "weight": 13 }, { "by": 6, "eat-app": 66, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "tablecheck": 72, "weight": 13 }, { "by": 3, "eat-app": 43, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "tablecheck": 46, "weight": 14 }, { "by": 15, "eat-app": 15, "edge": "eat-app", "key": "payments", "name": "Payments \u0026 pricing", "tablecheck": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "eat-app": 40, "edge": "eat-app", "key": "maintenance", "name": "Maintenance \u0026 community", "tablecheck": 35, "weight": 7 }, { "by": 14, "eat-app": 52, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "tablecheck": 66, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments \u0026 pricing and maintenance \u0026 community. 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.", "tablecheck": "TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck", "json": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md", "slim": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments \u0026 pricing and maintenance \u0026 community. Both do restaurant reservations.\n\n- Eat App Partner API: grade D, 53.4/100, rank #759 of 1094. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json\n- TableCheck API: grade C, 57.1/100, rank #666 of 1094. Markdown https://www.anchorterminal.com/tools/tablecheck.md · JSON https://www.anchorterminal.com/api/v1/tools/tablecheck.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- Payments \u0026 pricing, 15 against 0\n- Maintenance \u0026 community, 40 against 35\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\n\n### TableCheck API (C)\n\nGood for: Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.\n\nAhead on:\n- Schema \u0026 documentation, 77 against 59\n- Agent ergonomics, 72 against 66\n- Transparency \u0026 trust, 66 against 52\n\nWatch for: Access needs an emailed application, case-by-case approval and fees quoted privately\n\n\n## Score by category\n\n| Category | Weight | Eat App Partner API | TableCheck API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 80 | TableCheck API +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 77 | TableCheck API +18 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 72 | TableCheck API +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 46 | TableCheck API +3 |\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 | 35 | Eat App Partner API +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 66 | TableCheck API +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53.4 · D** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | Eat App Partner API | TableCheck API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat App (EAT APPLICATION DMCC) | TableCheck Inc. |\n| Hosted endpoint | `https://api.eatapp.co/partners/v2` | `https://api.tablecheck.com/api/` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\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 under the TableCheck API Terms of Service |\n| Tools exposed | none | 20 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | no |\n| Last release | 2026-10-13 | none |\n| Terms last updated | 2025-09-10 | 2022-10-11 |\n| Privacy policy last updated | no date given | 2016-12-14 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | 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**TableCheck API.** TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.\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### TableCheck API\n\n1. Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue\n2. Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it\n3. Call `hold_table` (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes\n4. Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from `list_shops`\n5. Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429\n\n## Questions\n\n### Which is better for AI agents, Eat App Partner API or TableCheck API?\n\nTableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Eat App Partner API and TableCheck API need an API key?\n\nEat App Partner API takes an API key or an OAuth sign-in. TableCheck API needs an API key.\n\n### Can an agent call Eat App Partner API and TableCheck API without installing anything?\n\nYes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and TableCheck API at https://api.tablecheck.com/api/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-app\", \"b\": \"tablecheck\"}`. From a terminal: `anchor compare eat-app tablecheck`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-app.json and https://www.anchorterminal.com/api/v1/tools/tablecheck.json\n\n## Other comparisons with Eat App Partner API or TableCheck API\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.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- [Eat App Partner API vs SevenRooms](https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.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 TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)\n- [TableCheck API vs Tock](https://www.anchorterminal.com/compare/tablecheck-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 TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md)\n- [Square Appointments (Bookings API) vs TableCheck API](https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.md)\n- [TableCheck API vs TheFork B2B API](https://www.anchorterminal.com/compare/tablecheck-vs-thefork.md)\n- [SevenRooms vs TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-15", "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", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Eat App Partner API vs TableCheck API", "url": "" } ], "description": "TableCheck scores 57.1 (C) to Eat App Partner's 53.4 (D) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat App Partner API D 53.4", "TableCheck API C 57.1", "scores" ], "h1": "Eat App Partner API vs TableCheck API", "image": "https://www.anchorterminal.com/assets/og/compare-eat-app-vs-tablecheck.png", "path": "/compare/eat-app-vs-tablecheck", "published": "2026-10-01", "section": "tools", "title": "Eat App Partner vs TableCheck for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-15", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck" }, "tokens": { "markdown": 2250, "slim": 630 }, "version": 1 }