{ "data": { "a": { "slug": "eat-app", "name": "Eat App Partner API", "vendor": "Eat App (EAT APPLICATION DMCC)", "vendorUrl": "https://restaurant.eatapp.co", "kind": "http-api", "category": "local-bookings", "summary": "Eat App is a restaurant reservation and table management system. Its Partner API lets booking channels check availability and create, change and cancel reservations, a Concierge API serves restaurant groups, and a read-only Restaurant MCP server connects AI assistants.", "url": "https://www.anchorterminal.com/tools/eat-app", "markdownUrl": "https://www.anchorterminal.com/tools/eat-app.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/eat-app.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/eat-app.json", "license": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements", "transports": [ "http" ], "remoteUrl": "https://api.eatapp.co/partners/v2", "packages": [], "auth": "mixed", "authNotes": "Partner approval required for the Partner API. A booking channel asks to become a partner (info@eatapp.co), Eat App activates partnerships restaurant by restaurant, and its support team issues a long-term API key sent as a Bearer token. A login endpoint also exchanges the partner's email and password for a 24-hour token. Concierge API keys are created by Eat App for restaurant groups. The Restaurant MCP server uses OAuth with dynamic client registration, PKCE and a single `mcp` scope, and the restaurant signs in with its Eat App login.", "pricing": "paid", "pricingNotes": "No per-call price. The pricing page marks API access in the Enterprise column only (Let's talk) and lists API and webhooks access as an add-on. Table management plans are $99, $199 and $389 a month, or $69, $159 and $299 billed yearly, with a 14-day trial and a $0 plan limited to 100 guests a month. The Restaurant MCP needs an active table management subscription. A sandbox host (api.eat-sandbox.co) is given to partners (https://restaurant.eatapp.co/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Partner or Concierge API docs, the MCP guide or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "mcp", "oauth", "sandbox", "status-page", "webhooks", "restaurants" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 53.4, "grade": "D", "agentReady": false, "rank": 752, "ranked": true, "rankOf": 1076, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.", "bestFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "strengths": [ "idempotency_token on Create Reservation returns the first success for a repeated request", "60 requests a minute stated, with a documented 429 body", "Better Stack status page with separate Partner API and Concierge API components and incident history", "Dated API changelog, latest entry 13 October 2026", "Restaurant MCP server with OAuth dynamic client registration and read-only access" ], "weaknesses": [ "A booking channel can book only at restaurants whose partnership Eat App has activated", "API access sits in the Enterprise column of the pricing page, priced through sales", "No OpenAPI file, llms.txt or SDK, only Postman collections", "A login endpoint accepts the partner's email and password for a 24-hour token", "No security.txt, and the trust centre content did not load for our reader" ], "agentNotes": [ "Send a unique idempotency_token with each new booking so a retry returns the first result", "Use POST /partners/v2/availability/range, not the legacy availability endpoint", "Keep include_tables ranges to 24 hours or less and pass covers with it", "Stay under 60 requests a minute and wait for the next minute after a 429", "Cancel by PATCH with status canceled, after which the reservation can no longer change" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 32 }, "provenanceScore": 71 }, "connect": { "http": "curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/eat-app" }, "area": "everyday", "provenance": { "legalEntity": "EAT APPLICATION DMCC", "domain": "eatapp.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://restaurant.eatapp.co/terms", "privacy": "https://restaurant.eatapp.co/privacy", "statusPage": "https://status.eatapp.co", "changelog": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of service (effective 10 September 2025) are entered into by EAT APPLICATION DMCC, Jumeirah Lake Towers, Dubai, licence DMCC-164040, and say the agreement also includes one executed with its licensee Swiggy Limited.", "The privacy policy names EAT APPLICATION DMCC and covers GDPR rights and a retention statement without fixed periods.", "The API changelog is a section of the Partner API Postman documentation.", "security.txt returns 404 on eatapp.co, restaurant.eatapp.co and api.eatapp.co. A trust centre at trust.eatapp.co loads by script and showed only its title to our reader.", "RDAP for eatapp.co did not answer, so the registration date is not recorded." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/eat-app.json", "live": { "slug": "eat-app", "probe": { "target": "https://api.eatapp.co/partners/v2", "method": "get", "lastAt": "2026-10-14T09:41:49.444870422Z", "lastOk": true, "lastStatus": 404, "lastMs": 157, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 175, "p95ms24h": 322, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.eatapp.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:05.16851429Z" }, "updatedAt": "2026-10-14T09:41:49.444870422Z" } }, "answer": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 6 of 7 scored categories. Eat App Partner API leads on reliability.", "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": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat App (EAT APPLICATION DMCC)", "b": "Block, Inc.", "name": "Vendor" }, { "a": "https://api.eatapp.co/partners/v2", "b": "https://connect.squareup.com/v2/bookings", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements", "b": "Proprietary service under the 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": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-13", "b": "2026-09-16", "name": "Last release" }, { "a": "2025-09-10", "b": "2026-09-10", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-09-15", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 6 of 7 scored categories. Eat App Partner API leads on reliability.", "question": "Which is better for AI agents, Eat App Partner API or Square Appointments (Bookings API)?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Eat App Partner API and Square Appointments (Bookings API) need an API key?" }, { "answer": "Yes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and Square Appointments (Bookings API) at https://connect.squareup.com/v2/bookings.", "question": "Can an agent call Eat App Partner API and Square Appointments (Bookings API) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 78 against 55" ], "also": null, "goodFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "slug": "eat-app", "watchFor": "A booking channel can book only at restaurants whose partnership Eat App has activated" }, { "aheadOn": [ "Schema \u0026 documentation, 89 against 59", "Agent ergonomics, 80 against 66", "Security \u0026 auth, 70 against 43", "Payments \u0026 pricing, 40 against 15", "Maintenance \u0026 community, 71 against 40", "Transparency \u0026 trust, 70 against 52" ], "also": [ "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-eat-app.json", "title": "Chope vs Eat App Partner API", "url": "https://www.anchorterminal.com/compare/chope-vs-eat-app" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.json", "title": "Eat App Partner API vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-resy.json", "title": "Eat App Partner API vs Resy", "url": "https://www.anchorterminal.com/compare/eat-app-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.json", "title": "Eat App Partner API vs SevenRooms", "url": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json", "title": "Eat App Partner API vs TableCheck API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-thefork.json", "title": "Eat App Partner API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-tock.json", "title": "Eat App Partner API vs Tock", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/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/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/resy-vs-square-appointments.json", "title": "Resy vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/resy-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": 23, "eat-app": 78, "edge": "eat-app", "key": "reliability", "name": "Reliability", "square-appointments": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 30, "eat-app": 59, "edge": "square-appointments", "key": "schema", "name": "Schema \u0026 documentation", "square-appointments": 89, "weight": 13 }, { "by": 14, "eat-app": 66, "edge": "square-appointments", "key": "ergonomics", "name": "Agent ergonomics", "square-appointments": 80, "weight": 13 }, { "by": 27, "eat-app": 43, "edge": "square-appointments", "key": "security", "name": "Security \u0026 auth", "square-appointments": 70, "weight": 14 }, { "by": 25, "eat-app": 15, "edge": "square-appointments", "key": "payments", "name": "Payments \u0026 pricing", "square-appointments": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 31, "eat-app": 40, "edge": "square-appointments", "key": "maintenance", "name": "Maintenance \u0026 community", "square-appointments": 71, "weight": 7 }, { "by": 18, "eat-app": 52, "edge": "square-appointments", "key": "transparency", "name": "Transparency \u0026 trust", "square-appointments": 70, "weight": 7 } ], "summary": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 6 of 7 scored categories. Eat App Partner API leads on reliability. Both do booking availability.", "verdicts": { "eat-app": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.", "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/eat-app-vs-square-appointments", "json": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md", "slim": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.min.md" }, "markdown": "Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 6 of 7 scored categories. Eat App Partner API leads on reliability. Both do booking availability.\n\n- Eat App Partner API: grade D, 53.4/100, rank #752 of 1076. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json\n- 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### Eat App Partner API (D)\n\nGood for: Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.\n\nAhead on:\n- Reliability, 78 against 55\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\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- Schema \u0026 documentation, 89 against 59\n- Agent ergonomics, 80 against 66\n- Security \u0026 auth, 70 against 43\n- Payments \u0026 pricing, 40 against 15\n- Maintenance \u0026 community, 71 against 40\n- Transparency \u0026 trust, 70 against 52\n\nAlso in its favour:\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 | Eat App Partner API | Square Appointments (Bookings API) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 55 | Eat App Partner API +23 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 89 | Square Appointments (Bookings API) +30 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 80 | Square Appointments (Bookings API) +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 70 | Square Appointments (Bookings API) +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | Square Appointments (Bookings API) +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 71 | Square Appointments (Bookings API) +31 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 70 | Square Appointments (Bookings API) +18 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53.4 · D** | **68.1 · B** | |\n\n## Facts side by side\n\n| Fact | Eat App Partner API | Square Appointments (Bookings API) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat App (EAT APPLICATION DMCC) | Block, Inc. |\n| Hosted endpoint | `https://api.eatapp.co/partners/v2` | `https://connect.squareup.com/v2/bookings` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service under the 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 | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-13 | 2026-09-16 |\n| Terms last updated | 2025-09-10 | 2026-09-10 |\n| Privacy policy last updated | no date given | 2026-09-15 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## Verdicts\n\n**Eat App Partner API.** A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.\n\n**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### Eat App Partner API\n\n1. Send a unique idempotency_token with each new booking so a retry returns the first result\n2. Use POST /partners/v2/availability/range, not the legacy availability endpoint\n3. Keep include_tables ranges to 24 hours or less and pass covers with it\n4. Stay under 60 requests a minute and wait for the next minute after a 429\n5. Cancel by PATCH with status canceled, after which the reservation can no longer change\n\n### 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, Eat App Partner API or Square Appointments (Bookings API)?\n\nSquare Appointments (Bookings API) scores 68.1 (B) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 6 of 7 scored categories. Eat App Partner API leads on reliability.\n\n### Do Eat App Partner API and Square Appointments (Bookings API) need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Eat App Partner API and Square Appointments (Bookings API) without installing anything?\n\nYes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and Square Appointments (Bookings API) at https://connect.squareup.com/v2/bookings.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-app\", \"b\": \"square-appointments\"}`. From a terminal: `anchor compare eat-app square-appointments`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-app.json and https://www.anchorterminal.com/api/v1/tools/square-appointments.json\n\n## Other comparisons with Eat App Partner API or Square Appointments (Bookings API)\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [Eat App Partner API vs SevenRooms](https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.md)\n- [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md)\n- [Eat App Partner API vs TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Eat App Partner API vs Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.md)\n- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.md)\n- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md)\n- [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-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": "Eat App Partner API vs Square Appointments (Bookings API)", "url": "" } ], "description": "Square Appointments scores 68.1 (B) to Eat App Partner's 53.4 (D) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat App Partner API D 53.4", "Square Appointments (Bookings API) B 68.1", "scores" ], "h1": "Eat App Partner API vs Square Appointments (Bookings API)", "image": "https://www.anchorterminal.com/assets/og/compare-eat-app-vs-square-appointments.png", "path": "/compare/eat-app-vs-square-appointments", "published": "2026-10-01", "section": "tools", "title": "Eat App Partner vs Square Appointments for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments" }, "tokens": { "markdown": 2400, "slim": 730 }, "version": 1 }