{ "data": { "a": { "slug": "resy", "name": "Resy", "vendor": "Resy (American Express)", "vendorUrl": "https://resy.com", "kind": "platform", "category": "local-bookings", "summary": "Resy is American Express's restaurant reservation app and website for diners, with Resy OS for venues. Since 11 August 2026 it also lists Tock's restaurants, wineries and experiences, over 25,000 venues in all.", "url": "https://www.anchorterminal.com/tools/resy", "markdownUrl": "https://www.anchorterminal.com/tools/resy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/resy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/resy.json", "license": "Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock", "transports": [], "packages": [], "auth": "oauth", "authNotes": "No public agent access. An MCP endpoint at https://apigw.americanexpress.com/dining/v1/mcp answers 401 and publishes OAuth metadata with one scope, 600003928_DINING_RESY_MCP_APPS. Its authorisation server supports only client_secret_jwt client authentication and lists no registration endpoint, so only clients American Express has registered can connect. No public documentation for it was found.", "pricing": "paid", "pricingNotes": "No prices for venues or for API access were found on resy.com/join, which asks venues to book a demo. Diner pricing could not be read, because resy.com renders by script.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on resy.com/join or the MCP endpoint's OAuth metadata (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "capabilities": [ "booking.reservations", "booking.availability", "booking.venue" ], "tags": [ "not-for-agents", "sales-led", "hosted", "closed-source", "partner-only", "ios", "android", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 10.3, "grade": "F", "agentReady": false, "rank": 1068, "ranked": true, "rankOf": 1076, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 25, "payments": 0, "reliability": 25, "schema": 0, "security": 3, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-14" }, "negative": 0, "verdict": "Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.", "bestFor": "Diners booking in person through the app.", "strengths": [ "Over 25,000 venues after Tock's restaurants, wineries and experiences joined on 11 August 2026", "Deposits, prepayment, card holds and verified bookings are available to venues, per the platform security page", "A dated product change in the last 90 days" ], "weaknesses": [ "No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients", "Resy's terms, privacy policy and status page render by script and could not be read", "No published prices for venues or partners", "Resy describes blocking bots and brokers at scale, so automated booking through the website is unwelcome" ], "agentNotes": [ "Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP", "Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 10.3 } ], "editorialScores": { "ergonomics": 0, "maintenance": 25, "payments": 0, "reliability": 25, "schema": 0, "security": 3, "transparency": 8 }, "provenanceScore": 52 }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/resy" }, "area": "everyday", "provenance": { "legalEntity": "Resy Network, Inc.", "domain": "resy.com", "domainRegistered": "2001-11-14", "endpointOnVendorDomain": false, "terms": "", "privacy": "https://resy.com/privacy", "statusPage": "https://status.resy.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "resy.com renders every path, including /privacy, /terms and /.well-known/security.txt, as the same script-driven page, so the privacy policy, terms and any security.txt were not read. The privacy URL is the one the business site's footer links.", "The business site's footer reads Resy Network, Inc. and links separate Resy and Tock privacy policies and merchant terms.", "status.resy.com loads by script and showed no components or history to our reader.", "The MCP endpoint sits on americanexpress.com, not resy.com.", "RDAP gives resy.com a registration date of 2001-11-14." ], "score": 52 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/resy.json", "live": { "slug": "resy", "vendorStatus": { "page": "https://status.resy.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:51.941824987Z" }, "updatedAt": "2026-10-14T08:53:51.941824987Z" } }, "answer": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category.", "b": { "slug": "square-appointments", "name": "Square Appointments (Bookings API)", "vendor": "Block, Inc.", "vendorUrl": "https://squareup.com/us/en/appointments", "kind": "http-api", "category": "local-bookings", "summary": "Square Appointments is Block's booking product for service businesses. Its Bookings API searches a seller's availability and creates, updates and cancels appointments, with location, team member and business booking profiles and custom attributes.", "url": "https://www.anchorterminal.com/tools/square-appointments", "markdownUrl": "https://www.anchorterminal.com/tools/square-appointments.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/square-appointments.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/square-appointments.json", "repo": "https://github.com/square/connect-api-specification", "license": "Proprietary service under the Square Developer Terms of Service. The OpenAPI specification and MCP server are Apache 2.0", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://connect.squareup.com/v2/bookings", "packages": [ { "registry": "npm", "name": "square" }, { "registry": "pypi", "name": "squareup" }, { "registry": "npm", "name": "square-mcp-server" } ], "auth": "mixed", "authNotes": "Self-serve. A Square account and a Developer Console application. OAuth access tokens carry appointment scopes (`APPOINTMENTS_READ`, `APPOINTMENTS_WRITE`, `APPOINTMENTS_ALL_READ`, `APPOINTMENTS_ALL_WRITE`, `APPOINTMENTS_BUSINESS_SETTINGS_READ`), expire after 30 days and can be refreshed and revoked. Personal access tokens are unrestricted for the owner's account. Seller-level permissions see every booking. Buyer-level permissions see only the bookings the app created (https://developer.squareup.com/docs/bookings-api/what-it-is).", "pricing": "freemium", "pricingNotes": "The API carries no charge. Square Free is $0 a month per location, Plus $49 and Premium $149, and the comparison table lists the Bookings API under Plus and Premium. Seller-level create, update and cancel need Plus or Premium, while buyer-level bookings work on the free plan. Card processing fees apply to payments. The sandbox is free (https://squareup.com/us/en/appointments/pricing, checked 2026-10-14).", "priceSummary": "$49 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in developer.squareup.com/llms.txt or the OpenAPI spec (checked 2026-10-14).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://developer.squareup.com/docs/bookings-api/what-it-is", "llmsTxt": "https://developer.squareup.com/llms.txt", "openapi": "https://raw.githubusercontent.com/square/connect-api-specification/master/api.json", "capabilities": [ "booking.appointments", "booking.availability", "booking.venue" ], "tags": [ "hosted", "closed-source", "rest", "oauth", "openapi", "llms-txt", "webhooks", "sandbox", "mcp", "freemium", "status-page", "bug-bounty", "venue-side" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 68.1, "grade": "B", "agentReady": false, "rank": 242, "ranked": true, "rankOf": 1076, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 71, "payments": 40, "reliability": 55, "schema": 89, "security": 70, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "The Bookings API lets an agent working for a Square seller search availability and create, change and cancel appointments, with a public OpenAPI spec, appointment OAuth scopes and idempotency keys. It acts for the venue. Seller-level writes need Plus or Premium, services with a no-show fee can't be booked through it, and it hasn't changed since September 2024.", "bestFor": "Venue-side appointment booking for salons, clinics and other service businesses already on Square.", "strengths": [ "Availability search, create, update and cancel are separate documented operations, all generally available", "Five appointment OAuth scopes separate reading, writing and business settings", "`idempotency_key` on create, update and cancel, and `booking_version` for optimistic locking", "Buyer-level permissions work on the free Appointments plan and limit an app to its own bookings", "Free sandbox, and Square's MCP server includes the bookings service" ], "weaknesses": [ "Seller-level create, update and cancel fail with 403 unless the seller pays for Plus ($49) or Premium ($149) per location", "Services with a non-zero no-show fee cannot be booked through the API, and the fee can't be set through it", "No Bookings API change in the changelog since 19 September 2024", "No numeric REST rate limits or SLA were found", "Bookable team members can only be set in the Square Dashboard" ], "agentNotes": [ "Act for the seller. This API books into one Square seller's calendar, not across businesses", "Call RetrieveBusinessBookingProfile and check `support_seller_level_writes` before trying to create or cancel a seller-level booking", "Call SearchAvailability first, then CreateBooking with the service variation ID and version, team member, location and customer", "Send a fresh `idempotency_key` on each create, update or cancel, and pass `booking_version` when cancelling", "Check `no_show_fee` on the service. A service with a non-zero fee must be booked by the customer elsewhere" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.1 } ], "editorialScores": { "ergonomics": 80, "maintenance": 71, "payments": 40, "reliability": 55, "schema": 89, "security": 70, "transparency": 56 }, "provenanceScore": 84 }, "connect": { "install": "npx square-mcp-server start", "http": "curl https://connect.squareupsandbox.com/v2/bookings/availability/search \\\n -X POST \\\n -H 'Square-Version: 2026-09-16' \\\n -H 'Authorization: Bearer {SANDBOX_ACCESS_TOKEN}' \\\n -H 'Content-Type: application/json' \\\n -d '{\"query\": {\"filter\": {\"start_at_range\": {\"start_at\": \"2026-10-20T09:00:00Z\", \"end_at\": \"2026-10-21T09:00:00Z\"}, \"location_id\": \"{LOCATION_ID}\"}}}'" }, "letme": { "capability": "https://letme.dev/booking.appointments", "tool": "https://letme.dev/square-appointments" }, "sameCompany": [ "square" ], "area": "everyday", "unitPrices": [ { "item": "Square Free", "unit": "month", "usd": 0, "note": "per location, buyer-level bookings only" }, { "item": "Square Plus", "unit": "month", "usd": 49, "note": "per location, Bookings API seller-level writes" }, { "item": "Square Premium", "unit": "month", "usd": 149, "note": "per location" } ], "provenance": { "legalEntity": "Block, Inc.", "domain": "squareup.com", "domainRegistered": "2007-05-26", "endpointOnVendorDomain": true, "terms": "https://squareup.com/us/en/legal/general/developers", "privacy": "https://squareup.com/us/en/legal/general/privacy", "statusPage": "https://www.issquareup.com", "changelog": "https://developer.squareup.com/docs/changelog/connect", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Square Developer Terms (updated 10 September 2026) are an agreement with Block, Inc. and govern the APIs, as recorded for the Square listing on 8 October 2026.", "The privacy notice (updated 15 September 2026) names Block, Inc., 1955 Broadway, Suite 600, Oakland, CA 94612 for US sellers.", "squareup.com/.well-known/security.txt returned 404 on 8 October 2026, and developer.squareup.com disallows /.well-known/ in robots.txt.", "RDAP gives a registration date of 2007-05-26 for squareup.com." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/square-appointments.json", "live": { "slug": "square-appointments", "probe": { "target": "https://connect.squareup.com/v2/bookings", "method": "get", "lastAt": "2026-10-14T09:42:08.775837061Z", "lastOk": true, "lastStatus": 401, "lastMs": 208, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 208, "p95ms24h": 362, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://www.issquareup.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:42.071528314Z" }, "updatedAt": "2026-10-14T09:42:08.775837061Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Resy (American Express)", "b": "Block, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://connect.squareup.com/v2/bookings", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock", "b": "Proprietary service under the Square Developer Terms of Service. The OpenAPI specification and MCP server are Apache 2.0", "name": "Licence" }, { "a": "none", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-16", "name": "Last release" }, { "a": "no document linked", "b": "2026-09-10", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-09-15", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "yes", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category.", "question": "Which is better for AI agents, Resy or Square Appointments (Bookings API)?" }, { "answer": "No hosted endpoint is listed for Resy. Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings.", "question": "Can an agent call Resy and Square Appointments (Bookings API) without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Diners booking in person through the app.", "slug": "resy", "watchFor": "No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients" }, { "aheadOn": [ "Reliability, 55 against 25", "Schema \u0026 documentation, 89 against 0", "Agent ergonomics, 80 against 0", "Security \u0026 auth, 70 against 3", "Payments \u0026 pricing, 40 against 0", "Maintenance \u0026 community, 71 against 25", "Transparency \u0026 trust, 70 against 30" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Venue-side appointment booking for salons, clinics and other service businesses already on Square.", "slug": "square-appointments", "watchFor": "Seller-level create, update and cancel fail with 403 unless the seller pays for Plus ($49) or Premium ($149) per location" } ], "job": { "capability": "booking.availability", "name": "Booking availability" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-resy.json", "title": "Chope vs Resy", "url": "https://www.anchorterminal.com/compare/chope-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-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/resy-vs-sevenrooms.json", "title": "Resy vs SevenRooms", "url": "https://www.anchorterminal.com/compare/resy-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-tablecheck.json", "title": "Resy vs TableCheck API", "url": "https://www.anchorterminal.com/compare/resy-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-thefork.json", "title": "Resy vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/resy-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-tock.json", "title": "Resy vs Tock", "url": "https://www.anchorterminal.com/compare/resy-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-square-appointments.json", "title": "Chope vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/chope-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.json", "title": "Eat App Partner API vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-resy.json", "title": "OpenTable APIs vs Resy", "url": "https://www.anchorterminal.com/compare/opentable-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments.json", "title": "OpenTable APIs vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments" }, { "json": "https://www.anchorterminal.com/compare/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/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/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/square-appointments-vs-tock.json", "title": "Square Appointments (Bookings API) vs Tock", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-tock" } ], "scores": [ { "by": 30, "edge": "square-appointments", "key": "reliability", "name": "Reliability", "resy": 25, "square-appointments": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 89, "edge": "square-appointments", "key": "schema", "name": "Schema \u0026 documentation", "resy": 0, "square-appointments": 89, "weight": 13 }, { "by": 80, "edge": "square-appointments", "key": "ergonomics", "name": "Agent ergonomics", "resy": 0, "square-appointments": 80, "weight": 13 }, { "by": 67, "edge": "square-appointments", "key": "security", "name": "Security \u0026 auth", "resy": 3, "square-appointments": 70, "weight": 14 }, { "by": 40, "edge": "square-appointments", "key": "payments", "name": "Payments \u0026 pricing", "resy": 0, "square-appointments": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 46, "edge": "square-appointments", "key": "maintenance", "name": "Maintenance \u0026 community", "resy": 25, "square-appointments": 71, "weight": 7 }, { "by": 40, "edge": "square-appointments", "key": "transparency", "name": "Transparency \u0026 trust", "resy": 30, "square-appointments": 70, "weight": 7 } ], "summary": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category. Both do booking availability.", "verdicts": { "resy": "Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.", "square-appointments": "The Bookings API lets an agent working for a Square seller search availability and create, change and cancel appointments, with a public OpenAPI spec, appointment OAuth scopes and idempotency keys. It acts for the venue. Seller-level writes need Plus or Premium, services with a no-show fee can't be booked through it, and it hasn't changed since September 2024." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/resy-vs-square-appointments", "json": "https://www.anchorterminal.com/compare/resy-vs-square-appointments.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/resy-vs-square-appointments.md", "slim": "https://www.anchorterminal.com/compare/resy-vs-square-appointments.min.md" }, "markdown": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category. Both do booking availability.\n\n- Resy: grade F, 10.3/100, rank #1068 of 1076. Markdown https://www.anchorterminal.com/tools/resy.md · JSON https://www.anchorterminal.com/api/v1/tools/resy.json\n- Square Appointments (Bookings API): grade B, 68.1/100, rank #242 of 1076. Markdown https://www.anchorterminal.com/tools/square-appointments.md · JSON https://www.anchorterminal.com/api/v1/tools/square-appointments.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### Resy (F)\n\nGood for: Diners booking in person through the app.\n\nWatch for: No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients\n\n### Square Appointments (Bookings API) (B)\n\nGood for: Venue-side appointment booking for salons, clinics and other service businesses already on Square.\n\nAhead on:\n- Reliability, 55 against 25\n- Schema \u0026 documentation, 89 against 0\n- Agent ergonomics, 80 against 0\n- Security \u0026 auth, 70 against 3\n- Payments \u0026 pricing, 40 against 0\n- Maintenance \u0026 community, 71 against 25\n- Transparency \u0026 trust, 70 against 30\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Seller-level create, update and cancel fail with 403 unless the seller pays for Plus ($49) or Premium ($149) per location\n\n\n## Score by category\n\n| Category | Weight | Resy | Square Appointments (Bookings API) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 25 | 55 | Square Appointments (Bookings API) +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 89 | Square Appointments (Bookings API) +89 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 80 | Square Appointments (Bookings API) +80 |\n| Security \u0026 auth | 14% (17.5 this run) | 3 | 70 | Square Appointments (Bookings API) +67 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 40 | Square Appointments (Bookings API) +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 25 | 71 | Square Appointments (Bookings API) +46 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 70 | Square Appointments (Bookings API) +40 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **10.3 · F** | **68.1 · B** | |\n\n## Facts side by side\n\n| Fact | Resy | Square Appointments (Bookings API) |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Resy (American Express) | Block, Inc. |\n| Hosted endpoint | no (local only) | `https://connect.squareup.com/v2/bookings` |\n| Transports | | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock | Proprietary service under the Square Developer Terms of Service. The OpenAPI specification and MCP server are Apache 2.0 |\n| Tools exposed | none | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-09-16 |\n| Terms last updated | no document linked | 2026-09-10 |\n| Privacy policy last updated | couldn't be read | 2026-09-15 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | yes |\n| Terms restrict benchmarking | | yes |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | yes |\n\n## Verdicts\n\n**Resy.** Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.\n\n**Square Appointments (Bookings API).** The Bookings API lets an agent working for a Square seller search availability and create, change and cancel appointments, with a public OpenAPI spec, appointment OAuth scopes and idempotency keys. It acts for the venue. Seller-level writes need Plus or Premium, services with a no-show fee can't be booked through it, and it hasn't changed since September 2024.\n\n## Before you call either\n\n### Resy\n\n1. Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP\n2. Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking\n\n### Square Appointments (Bookings API)\n\n1. Act for the seller. This API books into one Square seller's calendar, not across businesses\n2. Call RetrieveBusinessBookingProfile and check `support_seller_level_writes` before trying to create or cancel a seller-level booking\n3. Call SearchAvailability first, then CreateBooking with the service variation ID and version, team member, location and customer\n4. Send a fresh `idempotency_key` on each create, update or cancel, and pass `booking_version` when cancelling\n5. Check `no_show_fee` on the service. A service with a non-zero fee must be booked by the customer elsewhere\n\n## Questions\n\n### Which is better for AI agents, Resy or Square Appointments (Bookings API)?\n\nSquare Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category.\n\n### Can an agent call Resy and Square Appointments (Bookings API) without installing anything?\n\nNo hosted endpoint is listed for Resy. Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/resy-vs-square-appointments.json, and with the fewest tokens: https://www.anchorterminal.com/compare/resy-vs-square-appointments.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"resy\", \"b\": \"square-appointments\"}`. From a terminal: `anchor compare resy square-appointments`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/resy.json and https://www.anchorterminal.com/api/v1/tools/square-appointments.json\n\n## Other comparisons with Resy or Square Appointments (Bookings API)\n\n- [Chope vs Resy](https://www.anchorterminal.com/compare/chope-vs-resy.md)\n- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md)\n- [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)\n- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)\n- [Resy vs Tock](https://www.anchorterminal.com/compare/resy-vs-tock.md)\n- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.md)\n- [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md)\n- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md)\n- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md)\n- [Square Appointments (Bookings API) vs TableCheck API](https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.md)\n- [Square Appointments (Bookings API) vs TheFork B2B API](https://www.anchorterminal.com/compare/square-appointments-vs-thefork.md)\n- [SevenRooms vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments.md)\n- [Square Appointments (Bookings API) vs Tock](https://www.anchorterminal.com/compare/square-appointments-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": "Resy vs Square Appointments (Bookings API)", "url": "" } ], "description": "Square Appointments scores 68.1 (B) to Resy's 10.3 (F) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Resy F 10.3", "Square Appointments (Bookings API) B 68.1", "scores" ], "h1": "Resy vs Square Appointments (Bookings API)", "image": "https://www.anchorterminal.com/assets/og/compare-resy-vs-square-appointments.png", "path": "/compare/resy-vs-square-appointments", "published": "2026-10-01", "section": "tools", "title": "Resy vs Square Appointments for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/resy-vs-square-appointments" }, "tokens": { "markdown": 2200, "slim": 730 }, "version": 1 }