{
  "data": {
    "a": {
      "slug": "chope",
      "name": "Chope",
      "vendor": "The Chope Group Pte Ltd",
      "vendorUrl": "https://www.chope.co",
      "kind": "platform",
      "category": "local-bookings",
      "summary": "Chope is a restaurant reservation website and app for diners in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab. Diners search restaurants, book tables and pay deposits where a restaurant asks for one.",
      "url": "https://www.anchorterminal.com/tools/chope",
      "markdownUrl": "https://www.anchorterminal.com/tools/chope.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/chope.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/chope.json",
      "license": "Proprietary service under Chope's Terms \u0026 Conditions",
      "transports": [],
      "packages": [],
      "auth": "mixed",
      "authNotes": "No developer access. Diners sign up with an email or Facebook, or book as a guest and manage the booking with a confirmation code (https://www.chope.co/singapore-restaurants/pages/dinerfaq).",
      "pricing": "free",
      "pricingNotes": "Free for diners, and the app is free on the App Store. Restaurants may ask for a deposit for set menus, large groups, particular days or occasions (https://www.chope.co/singapore-restaurants/pages/dinerfaq, checked 2026-10-14).",
      "priceSummary": "Free",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No API, so no x402, MPP or L402 (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "capabilities": [
        "booking.reservations",
        "booking.availability"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "not-for-agents",
        "ios",
        "android",
        "free",
        "diner-side"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 13.3,
        "grade": "F",
        "agentReady": false,
        "rank": 1057,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 0,
          "maintenance": 34,
          "payments": 30,
          "reliability": 15,
          "schema": 0,
          "security": 0,
          "transparency": 41
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.",
        "bestFor": "A person booking restaurants in Singapore, Thailand and Indonesia.",
        "strengths": [
          "Free for diners, with deposits set by each restaurant and explained in the diner FAQ",
          "iOS releases on 15 and 30 September 2026",
          "Dated notices for product changes, such as the end of Chope-Dollars from 15 October 2026"
        ],
        "weaknesses": [
          "No public API or MCP server that an outside agent can call",
          "The Terms \u0026 Conditions forbid spidering, scraping or mirroring without written permission",
          "No status page, security.txt or named processors, apart from Grab",
          "The privacy notice gives no retention periods"
        ],
        "agentNotes": [
          "Don't plan to call Chope from another agent. Hand the booking to the person, who can use the Chope site, the app or Grab Dine Out",
          "For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue",
          "Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 13.3
          }
        ],
        "editorialScores": {
          "ergonomics": 0,
          "maintenance": 34,
          "payments": 30,
          "reliability": 15,
          "schema": 0,
          "security": 0,
          "transparency": 43
        },
        "provenanceScore": 39
      },
      "letme": {
        "capability": "https://letme.dev/booking.reservations",
        "tool": "https://letme.dev/chope"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "The Chope Group Pte Ltd",
        "domain": "chope.co",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "https://www.chope.co/singapore-restaurants/tc",
        "privacy": "https://www.chope.co/singapore-restaurants/tc",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-14",
        "notes": [
          "The Terms \u0026 Conditions (last updated 11 September 2023) and the privacy notice (last updated 6 March 2025) are on one page with tabs.",
          "www.chope.co/.well-known/security.txt returns 404, and status.chope.co redirects to the home page.",
          "The RDAP registration date for chope.co was not returned."
        ],
        "score": 39
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/chope.json"
    },
    "answer": "Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability.",
    "b": {
      "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"
      }
    },
    "facts": [
      {
        "a": "Platform",
        "b": "Platform",
        "name": "Kind"
      },
      {
        "a": "The Chope Group Pte Ltd",
        "b": "Resy (American Express)",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Chope's Terms \u0026 Conditions",
        "b": "Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-30",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2023-09-11",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "2023-09-11",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability.",
        "question": "Which is better for AI agents, Chope or Resy?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Payments \u0026 pricing, 30 against 0",
          "Maintenance \u0026 community, 34 against 25",
          "Transparency \u0026 trust, 41 against 30"
        ],
        "also": null,
        "goodFor": "A person booking restaurants in Singapore, Thailand and Indonesia.",
        "slug": "chope",
        "watchFor": "No public API or MCP server that an outside agent can call"
      },
      {
        "aheadOn": [
          "Reliability, 25 against 15"
        ],
        "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"
      }
    ],
    "job": {
      "capability": "booking.reservations",
      "name": "Restaurant reservations"
    },
    "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/chope-vs-opentable.json",
        "title": "Chope vs OpenTable APIs",
        "url": "https://www.anchorterminal.com/compare/chope-vs-opentable"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms.json",
        "title": "Chope vs SevenRooms",
        "url": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chope-vs-tablecheck.json",
        "title": "Chope vs TableCheck API",
        "url": "https://www.anchorterminal.com/compare/chope-vs-tablecheck"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chope-vs-thefork.json",
        "title": "Chope vs TheFork B2B API",
        "url": "https://www.anchorterminal.com/compare/chope-vs-thefork"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chope-vs-tock.json",
        "title": "Chope vs Tock",
        "url": "https://www.anchorterminal.com/compare/chope-vs-tock"
      },
      {
        "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/opentable-vs-resy.json",
        "title": "OpenTable APIs vs Resy",
        "url": "https://www.anchorterminal.com/compare/opentable-vs-resy"
      },
      {
        "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"
      }
    ],
    "scores": [
      {
        "by": 10,
        "chope": 15,
        "edge": "resy",
        "key": "reliability",
        "name": "Reliability",
        "resy": 25,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "chope": 0,
        "edge": "",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "resy": 0,
        "weight": 13
      },
      {
        "by": 0,
        "chope": 0,
        "edge": "",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "resy": 0,
        "weight": 13
      },
      {
        "by": 3,
        "chope": 0,
        "edge": "resy",
        "key": "security",
        "name": "Security \u0026 auth",
        "resy": 3,
        "weight": 14
      },
      {
        "by": 30,
        "chope": 30,
        "edge": "chope",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "resy": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "chope": 34,
        "edge": "chope",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "resy": 25,
        "weight": 7
      },
      {
        "by": 11,
        "chope": 41,
        "edge": "chope",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "resy": 30,
        "weight": 7
      }
    ],
    "summary": "Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability. Both do restaurant reservations.",
    "verdicts": {
      "chope": "Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.",
      "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/chope-vs-resy",
    "json": "https://www.anchorterminal.com/compare/chope-vs-resy.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/chope-vs-resy.md",
    "slim": "https://www.anchorterminal.com/compare/chope-vs-resy.min.md"
  },
  "markdown": "Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability. Both do restaurant reservations.\n\n- Chope: grade F, 13.3/100, rank #1057 of 1076. Markdown https://www.anchorterminal.com/tools/chope.md · JSON https://www.anchorterminal.com/api/v1/tools/chope.json\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- 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### Chope (F)\n\nGood for: A person booking restaurants in Singapore, Thailand and Indonesia.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 0\n- Maintenance \u0026 community, 34 against 25\n- Transparency \u0026 trust, 41 against 30\n\nWatch for: No public API or MCP server that an outside agent can call\n\n### Resy (F)\n\nGood for: Diners booking in person through the app.\n\nAhead on:\n- Reliability, 25 against 15\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\n## Score by category\n\n| Category | Weight | Chope | Resy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 25 | Resy +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 0 | even |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 0 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 0 | 3 | Resy +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 0 | Chope +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 25 | Chope +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 30 | Chope +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **13.3 · F** | **10.3 · F** | |\n\n## Facts side by side\n\n| Fact | Chope | Resy |\n| --- | --- | --- |\n| Kind | Platform | Platform |\n| Vendor | The Chope Group Pte Ltd | Resy (American Express) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports |  |  |\n| Auth | OAuth or key | OAuth |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Chope's Terms \u0026 Conditions | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-09-30 | none |\n| Terms last updated | 2023-09-11 | no document linked |\n| Privacy policy last updated | 2023-09-11 | couldn't be read |\n| Customer content may train models | not found in the text |  |\n| Terms restrict automated access | yes |  |\n| Terms restrict benchmarking | not found in the text |  |\n| Terms or service can change without notice | yes |  |\n| Arbitration or class-action waiver | not found in the text |  |\n\n## Verdicts\n\n**Chope.** Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.\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## Before you call either\n\n### Chope\n\n1. Don't plan to call Chope from another agent. Hand the booking to the person, who can use the Chope site, the app or Grab Dine Out\n2. For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue\n3. Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size\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## Questions\n\n### Which is better for AI agents, Chope or Resy?\n\nChope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-resy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-resy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"chope\", \"b\": \"resy\"}`. From a terminal: `anchor compare chope resy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/resy.json\n\n## Other comparisons with Chope or Resy\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)\n- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.md)\n- [Chope vs Tock](https://www.anchorterminal.com/compare/chope-vs-tock.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- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md)\n- [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-vs-square-appointments.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": "Chope vs Resy",
        "url": ""
      }
    ],
    "description": "Chope scores 13.3 (F) to Resy's 10.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Chope F 13.3",
      "Resy F 10.3",
      "scores"
    ],
    "h1": "Chope vs Resy",
    "image": "https://www.anchorterminal.com/assets/og/compare-chope-vs-resy.png",
    "path": "/compare/chope-vs-resy",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Chope vs Resy for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/compare/chope-vs-resy"
  },
  "tokens": {
    "markdown": 1800,
    "slim": 580
  },
  "version": 1
}