{ "data": { "a": { "slug": "sevenrooms", "name": "SevenRooms", "vendor": "SevenRooms (a DoorDash company)", "vendorUrl": "https://sevenrooms.com", "kind": "platform", "category": "local-bookings", "summary": "SevenRooms is a reservation, table management, guest CRM and marketing platform for restaurants, hotels and other hospitality venues, owned by DoorDash. It runs venues' booking widgets and connects to 100+ booking, POS and voice AI partners.", "url": "https://www.anchorterminal.com/tools/sevenrooms", "markdownUrl": "https://www.anchorterminal.com/tools/sevenrooms.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sevenrooms.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sevenrooms.json", "license": "Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements", "transports": [], "packages": [], "auth": "mixed", "authNotes": "No public agent access. API documentation at api-docs.sevenrooms.com moved to individually provisioned accounts on 26 February, and new integrators are sent to a partnerships form. The credential type could not be read first-hand, because the reference sits behind that login.", "pricing": "paid", "pricingNotes": "No prices are published. The pricing page describes packages and asks for a demo (https://sevenrooms.com/pricing/). No free tier or self-serve trial was found.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on sevenrooms.com or the public part of the API docs (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://api-docs.sevenrooms.com", "llmsTxt": "https://api-docs.sevenrooms.com/llms.txt", "capabilities": [ "booking.venue", "booking.reservations", "booking.availability", "crm.records" ], "tags": [ "not-for-agents", "sales-led", "hosted", "closed-source", "partner-only", "status-page", "soc2", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 17.7, "grade": "F", "agentReady": false, "rank": 1043, "ranked": true, "rankOf": 1076, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 15, "payments": 0, "reliability": 40, "schema": 5, "security": 14, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.", "bestFor": "Hospitality venues and groups that want reservations, CRM and marketing in one system.", "strengths": [ "Statuspage history with a separate API component", "Trust centre lists SOC 2, PCI DSS, subprocessors and a responsible disclosure section", "Terms and privacy policy carry 2026 update dates and name the legal entity" ], "weaknesses": [ "No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account", "Venue-side only. Guests have no accounts, so nothing acts for a diner", "No published prices, free tier or self-serve trial", "One major outage of VMS and widgets on 7 September 2026" ], "agentNotes": [ "Don't plan to call SevenRooms from another agent. To book for a diner, use the venue's booking widget with the person, or a booking channel the venue lists", "If you work for a venue or vendor, apply through the SevenRooms partnerships form before planning an integration" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 17.7 } ], "editorialScores": { "ergonomics": 0, "maintenance": 15, "payments": 0, "reliability": 40, "schema": 5, "security": 14, "transparency": 40 }, "provenanceScore": 75 }, "letme": { "capability": "https://letme.dev/booking.venue", "tool": "https://letme.dev/sevenrooms" }, "area": "everyday", "provenance": { "legalEntity": "SEVENROOMS LLC", "domain": "sevenrooms.com", "domainRegistered": "2007-09-09", "endpointOnVendorDomain": true, "terms": "https://sevenrooms.com/terms-of-service/", "privacy": "https://sevenrooms.com/privacy-policy/", "statusPage": "https://status.sevenrooms.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms (updated 17 April 2026) and privacy policy (updated 16 June 2026) name SEVENROOMS LLC, a DoorDash Inc. company.", "sevenrooms.com/.well-known/security.txt returns 404. The trust centre at trust.sevenrooms.com (SafeBase) lists a responsible disclosure section.", "No public changelog was found. The API docs landing page says it was last updated about six months ago.", "RDAP gives sevenrooms.com a registration date of 2007-09-09." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sevenrooms.json", "live": { "slug": "sevenrooms", "vendorStatus": { "page": "https://status.sevenrooms.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:40.536180888Z" }, "updatedAt": "2026-10-14T09:39:40.536180888Z" } }, "answer": "TableCheck API scores 57.1 (C) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories.", "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": 661, "ranked": true, "rankOf": 1076, "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-14T09:42:09.492395571Z", "lastOk": true, "lastStatus": 200, "lastMs": 717, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 711, "p95ms24h": 871, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://tablecheck.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:43.550229393Z" }, "updatedAt": "2026-10-14T09:42:09.492395571Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "SevenRooms (a DoorDash company)", "b": "TableCheck Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.tablecheck.com/api/", "name": "Hosted endpoint" }, { "a": "", "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 the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements", "b": "Proprietary service under the TableCheck API Terms of Service", "name": "Licence" }, { "a": "none", "b": "20", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-04-17", "b": "2022-10-11", "name": "Terms last updated" }, { "a": "2026-06-16", "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": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, SevenRooms or TableCheck API?" }, { "answer": "No hosted endpoint is listed for SevenRooms. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.", "question": "Can an agent call SevenRooms and TableCheck API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Hospitality venues and groups that want reservations, CRM and marketing in one system.", "slug": "sevenrooms", "watchFor": "No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account" }, { "aheadOn": [ "Reliability, 80 against 40", "Schema \u0026 documentation, 77 against 5", "Agent ergonomics, 72 against 0", "Security \u0026 auth, 46 against 14", "Maintenance \u0026 community, 35 against 15", "Transparency \u0026 trust, 66 against 58" ], "also": [ "A hosted endpoint, with nothing to install" ], "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.venue", "name": "Venue management" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms.json", "title": "Chope vs SevenRooms", "url": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms" }, { "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-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/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/tablecheck-vs-tock.json", "title": "TableCheck API vs Tock", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.json", "title": "OpenTable APIs vs SevenRooms", "url": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-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-square-appointments.json", "title": "SevenRooms vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.json", "title": "SevenRooms vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock.json", "title": "SevenRooms vs Tock", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock" } ], "scores": [ { "by": 40, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "sevenrooms": 40, "tablecheck": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 72, "edge": "tablecheck", "key": "schema", "name": "Schema \u0026 documentation", "sevenrooms": 5, "tablecheck": 77, "weight": 13 }, { "by": 72, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "sevenrooms": 0, "tablecheck": 72, "weight": 13 }, { "by": 32, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "sevenrooms": 14, "tablecheck": 46, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "sevenrooms": 0, "tablecheck": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edge": "tablecheck", "key": "maintenance", "name": "Maintenance \u0026 community", "sevenrooms": 15, "tablecheck": 35, "weight": 7 }, { "by": 8, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "sevenrooms": 58, "tablecheck": 66, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. Both do venue management.", "verdicts": { "sevenrooms": "SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.", "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/sevenrooms-vs-tablecheck", "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.md", "slim": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. Both do venue management.\n\n- SevenRooms: grade F, 17.7/100, rank #1043 of 1076. Markdown https://www.anchorterminal.com/tools/sevenrooms.md · JSON https://www.anchorterminal.com/api/v1/tools/sevenrooms.json\n- TableCheck API: grade C, 57.1/100, rank #661 of 1076. 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### SevenRooms (F)\n\nGood for: Hospitality venues and groups that want reservations, CRM and marketing in one system.\n\nWatch for: No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account\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- Reliability, 80 against 40\n- Schema \u0026 documentation, 77 against 5\n- Agent ergonomics, 72 against 0\n- Security \u0026 auth, 46 against 14\n- Maintenance \u0026 community, 35 against 15\n- Transparency \u0026 trust, 66 against 58\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\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 | SevenRooms | TableCheck API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 80 | TableCheck API +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 5 | 77 | TableCheck API +72 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 72 | TableCheck API +72 |\n| Security \u0026 auth | 14% (17.5 this run) | 14 | 46 | TableCheck API +32 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 0 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 15 | 35 | TableCheck API +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 66 | TableCheck API +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **17.7 · F** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | SevenRooms | TableCheck API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | SevenRooms (a DoorDash company) | TableCheck Inc. |\n| Hosted endpoint | no (local only) | `https://api.tablecheck.com/api/` |\n| Transports | | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements | Proprietary service under the TableCheck API Terms of Service |\n| Tools exposed | none | 20 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Terms last updated | 2026-04-17 | 2022-10-11 |\n| Privacy policy last updated | 2026-06-16 | 2016-12-14 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n\n## Verdicts\n\n**SevenRooms.** SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.\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### SevenRooms\n\n1. Don't plan to call SevenRooms from another agent. To book for a diner, use the venue's booking widget with the person, or a booking channel the venue lists\n2. If you work for a venue or vendor, apply through the SevenRooms partnerships form before planning an integration\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, SevenRooms or TableCheck API?\n\nTableCheck API scores 57.1 (C) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories.\n\n### Can an agent call SevenRooms and TableCheck API without installing anything?\n\nNo hosted endpoint is listed for SevenRooms. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"sevenrooms\", \"b\": \"tablecheck\"}`. From a terminal: `anchor compare sevenrooms tablecheck`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sevenrooms.json and https://www.anchorterminal.com/api/v1/tools/tablecheck.json\n\n## Other comparisons with SevenRooms or TableCheck API\n\n- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.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- [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- [TableCheck API vs Tock](https://www.anchorterminal.com/compare/tablecheck-vs-tock.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.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 Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments.md)\n- [SevenRooms vs TheFork B2B API](https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.md)\n- [SevenRooms vs Tock](https://www.anchorterminal.com/compare/sevenrooms-vs-tock.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": "SevenRooms vs TableCheck API", "url": "" } ], "description": "TableCheck scores 57.1 (C) to SevenRooms's 17.7 (F) for venue management. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "SevenRooms F 17.7", "TableCheck API C 57.1", "scores" ], "h1": "SevenRooms vs TableCheck API", "image": "https://www.anchorterminal.com/assets/og/compare-sevenrooms-vs-tablecheck.png", "path": "/compare/sevenrooms-vs-tablecheck", "published": "2026-10-01", "section": "tools", "title": "SevenRooms vs TableCheck for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck" }, "tokens": { "markdown": 2100, "slim": 680 }, "version": 1 }