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