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