{ "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": "TheFork B2B API scores 43.6 (E) on agent readiness against SevenRooms's 17.7 (F), and leads in 4 of 7 scored categories. SevenRooms leads on reliability and transparency \u0026 trust.", "b": { "slug": "thefork", "name": "TheFork B2B API", "vendor": "TheFork (La Fourchette SAS)", "vendorUrl": "https://www.thefork.com", "kind": "http-api", "category": "local-bookings", "summary": "TheFork's B2B API lets restaurants and their software partners, such as CRM vendors and AI phone agents, read availability and create, change and cancel reservations in TheFork Manager, with webhooks, reviews and customer data.", "url": "https://www.anchorterminal.com/tools/thefork", "markdownUrl": "https://www.anchorterminal.com/tools/thefork.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thefork.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thefork.json", "license": "Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "transports": [ "http" ], "remoteUrl": "https://api.thefork.io/manager", "packages": [], "auth": "oauth", "authNotes": "Partner approval required. Credentials are requested from the integrations team at integrations@thefork.com with a company name and use case. TheFork sends a client_id and client_secret through a secure channel, and the client exchanges them at https://auth.thefork.io/oauth/token (OAuth 2.0 client credentials, audience https://api.thefork.io) for a Bearer token that lasts 8,600 seconds. Nine scopes limit each client, from full access (tfm-restaurant) to read-only availability. restaurantUuid and groupUuid values for each restaurant come from TheFork, as no endpoint lists them.", "pricing": "byo-plan", "pricingNotes": "No API prices are published. Access follows a partnership with TheFork, and the rate limit is set by contract. The API terms mention test data for pre-launch testing. No sandbox host or self-serve tier is documented (https://docs.thefork.io/getting-started).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, llms.txt or OpenAPI schema (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.thefork.io/B2B-API/introduction", "llmsTxt": "https://docs.thefork.io/B2B-API/llms.txt", "openapi": "https://api.thefork.io/manager/openapi.json", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "oauth", "openapi", "llms-txt", "webhooks", "eu", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 43.6, "grade": "E", "agentReady": false, "rank": 951, "ranked": true, "rankOf": 1076, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.", "bestFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "strengths": [ "OpenAPI 3.1 schema generated from the deployed code, with 19 operations, enums, examples and error responses", "llms.txt for the B2B API covers scopes per endpoint, time zones, reservation statuses and error formats", "Nine OAuth scopes, including read-only availability and a separate scope for unrestricted bookings that is off by default", "Business error codes such as NO_AVAILABILITY, DOUBLE_BOOKING and RESERVATION_NOT_FOUND", "Written versioning policy with 6 months of support for the previous version" ], "weaknesses": [ "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants", "Credentials come from the integrations team by email after approval, with no self-serve route", "Timeslots that need a payment guarantee cannot be booked through the API", "The status page at status.thefork.io redirects to a private Rootly page that needs a sign-in", "No changelog, idempotency key or published production rate limit" ], "agentNotes": [ "Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card", "Check the status field after creating a reservation and treat REQUESTED as unconfirmed", "Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time", "Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING", "Cache the access token for its 8,600 seconds and do not request a new one while it is valid" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 33 }, "provenanceScore": 60 }, "connect": { "http": "curl -X POST https://auth.thefork.io/oauth/token -H 'Content-Type: application/x-www-form-urlencoded' -d 'audience=https://api.thefork.io\u0026grant_type=client_credentials\u0026client_id=CLIENT_ID\u0026client_secret=CLIENT_SECRET'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/thefork" }, "area": "everyday", "provenance": { "legalEntity": "La Fourchette SAS", "domain": "thefork.io", "domainRegistered": "2016-05-30", "endpointOnVendorDomain": true, "terms": "https://docs.thefork.io/pdf/LaFourchette-Partners-API-Licence-2.pdf", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The developer portal footer links the TheFork Partners API Terms of Use, a PDF naming La Fourchette SAS, 70 rue Saint Lazare, Paris, company number 494 447 949, where no core agreement exists.", "www.thefork.com answered with a bot check (403), so its privacy policy and terms were not read and no privacy URL is recorded.", "status.thefork.io redirects to a private Rootly status page that needs a sign-in, so no public status page is recorded.", "www.thefork.com/.well-known/security.txt returns 404 and docs.thefork.io/.well-known/security.txt returns 403.", "No changelog was found. docs.thefork.io/changelog returns 403.", "RDAP gives thefork.io a registration date of 2016-05-30 and thefork.com 1998-11-04." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thefork.json", "live": { "slug": "thefork", "probe": { "target": "https://api.thefork.io/manager", "method": "get", "lastAt": "2026-10-14T09:42:10.255461561Z", "lastOk": true, "lastStatus": 404, "lastMs": 57, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 56, "p95ms24h": 119, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "updatedAt": "2026-10-14T09:42:10.255461561Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "SevenRooms (a DoorDash company)", "b": "TheFork (La Fourchette SAS)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.thefork.io/manager", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements", "b": "Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-04-17", "b": "", "name": "Terms last updated" }, { "a": "2026-06-16", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TheFork B2B API scores 43.6 (E) on agent readiness against SevenRooms's 17.7 (F), and leads in 4 of 7 scored categories. SevenRooms leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, SevenRooms or TheFork B2B API?" }, { "answer": "No hosted endpoint is listed for SevenRooms. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.", "question": "Can an agent call SevenRooms and TheFork B2B API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 40 against 35", "Transparency \u0026 trust, 58 against 47" ], "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": [ "Schema \u0026 documentation, 87 against 5", "Agent ergonomics, 56 against 0", "Security \u0026 auth, 42 against 14", "Payments \u0026 pricing, 5 against 0" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "slug": "thefork", "watchFor": "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants" } ], "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-thefork.json", "title": "Chope vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/chope-vs-thefork" }, { "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/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-thefork.json", "title": "Resy vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/resy-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/thefork-vs-tock.json", "title": "TheFork B2B API vs Tock", "url": "https://www.anchorterminal.com/compare/thefork-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-thefork.json", "title": "OpenTable APIs vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/opentable-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/square-appointments-vs-thefork.json", "title": "Square Appointments (Bookings API) vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-thefork" }, { "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-tablecheck.json", "title": "SevenRooms vs TableCheck API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck" }, { "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": 5, "edge": "sevenrooms", "key": "reliability", "name": "Reliability", "sevenrooms": 40, "thefork": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 82, "edge": "thefork", "key": "schema", "name": "Schema \u0026 documentation", "sevenrooms": 5, "thefork": 87, "weight": 13 }, { "by": 56, "edge": "thefork", "key": "ergonomics", "name": "Agent ergonomics", "sevenrooms": 0, "thefork": 56, "weight": 13 }, { "by": 28, "edge": "thefork", "key": "security", "name": "Security \u0026 auth", "sevenrooms": 14, "thefork": 42, "weight": 14 }, { "by": 5, "edge": "thefork", "key": "payments", "name": "Payments \u0026 pricing", "sevenrooms": 0, "thefork": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "key": "maintenance", "name": "Maintenance \u0026 community", "sevenrooms": 15, "thefork": 15, "weight": 7 }, { "by": 11, "edge": "sevenrooms", "key": "transparency", "name": "Transparency \u0026 trust", "sevenrooms": 58, "thefork": 47, "weight": 7 } ], "summary": "TheFork B2B API scores 43.6 (E) on agent readiness against SevenRooms's 17.7 (F), and leads in 4 of 7 scored categories. SevenRooms leads on reliability and transparency \u0026 trust. 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.", "thefork": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork", "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.md", "slim": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.min.md" }, "markdown": "TheFork B2B API scores 43.6 (E) on agent readiness against SevenRooms's 17.7 (F), and leads in 4 of 7 scored categories. SevenRooms leads on reliability and transparency \u0026 trust. 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- TheFork B2B API: grade E, 43.6/100, rank #951 of 1076. Markdown https://www.anchorterminal.com/tools/thefork.md · JSON https://www.anchorterminal.com/api/v1/tools/thefork.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\nAhead on:\n- Reliability, 40 against 35\n- Transparency \u0026 trust, 58 against 47\n\nWatch for: No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account\n\n### TheFork B2B API (E)\n\nGood for: CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.\n\nAhead on:\n- Schema \u0026 documentation, 87 against 5\n- Agent ergonomics, 56 against 0\n- Security \u0026 auth, 42 against 14\n- Payments \u0026 pricing, 5 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants\n\n\n## Score by category\n\n| Category | Weight | SevenRooms | TheFork B2B API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 35 | SevenRooms +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 5 | 87 | TheFork B2B API +82 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 56 | TheFork B2B API +56 |\n| Security \u0026 auth | 14% (17.5 this run) | 14 | 42 | TheFork B2B API +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 5 | TheFork B2B API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 15 | 15 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 47 | SevenRooms +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **17.7 · F** | **43.6 · E** | |\n\n## Facts side by side\n\n| Fact | SevenRooms | TheFork B2B API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | SevenRooms (a DoorDash company) | TheFork (La Fourchette SAS) |\n| Hosted endpoint | no (local only) | `https://api.thefork.io/manager` |\n| Transports | | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Your plan |\n| x402 | no | no |\n| Licence | Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements | Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Terms last updated | 2026-04-17 | |\n| Privacy policy last updated | 2026-06-16 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | yes | |\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**TheFork B2B API.** A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.\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### TheFork B2B API\n\n1. Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card\n2. Check the status field after creating a reservation and treat REQUESTED as unconfirmed\n3. Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time\n4. Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING\n5. Cache the access token for its 8,600 seconds and do not request a new one while it is valid\n\n## Questions\n\n### Which is better for AI agents, SevenRooms or TheFork B2B API?\n\nTheFork B2B API scores 43.6 (E) on agent readiness against SevenRooms's 17.7 (F), and leads in 4 of 7 scored categories. SevenRooms leads on reliability and transparency \u0026 trust.\n\n### Can an agent call SevenRooms and TheFork B2B API without installing anything?\n\nNo hosted endpoint is listed for SevenRooms. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"sevenrooms\", \"b\": \"thefork\"}`. From a terminal: `anchor compare sevenrooms thefork`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sevenrooms.json and https://www.anchorterminal.com/api/v1/tools/thefork.json\n\n## Other comparisons with SevenRooms or TheFork B2B API\n\n- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)\n- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.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- [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md)\n- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)\n- [TheFork B2B API vs Tock](https://www.anchorterminal.com/compare/thefork-vs-tock.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md)\n- [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md)\n- [Square Appointments (Bookings API) vs TheFork B2B API](https://www.anchorterminal.com/compare/square-appointments-vs-thefork.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 TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.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 TheFork B2B API", "url": "" } ], "description": "TheFork B2B scores 43.6 (E) to SevenRooms's 17.7 (F) for venue management. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "SevenRooms F 17.7", "TheFork B2B API E 43.6", "scores" ], "h1": "SevenRooms vs TheFork B2B API", "image": "https://www.anchorterminal.com/assets/og/compare-sevenrooms-vs-thefork.png", "path": "/compare/sevenrooms-vs-thefork", "published": "2026-10-01", "section": "tools", "title": "SevenRooms vs TheFork B2B for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork" }, "tokens": { "markdown": 2050, "slim": 680 }, "version": 1 }