{
  "data": {
    "a": {
      "slug": "opentable",
      "name": "OpenTable APIs",
      "vendor": "OpenTable",
      "vendorUrl": "https://www.opentable.com",
      "kind": "http-api",
      "category": "local-bookings",
      "summary": "OpenTable's partner APIs let approved partners search restaurant availability and make, change and cancel reservations, for diners through the Consumer API or for restaurants' voice agents through the In-House Booking API, with OAuth 2.0 client credentials.",
      "url": "https://www.anchorterminal.com/tools/opentable",
      "markdownUrl": "https://www.anchorterminal.com/tools/opentable.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opentable.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opentable.json",
      "license": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://platform.opentable.com",
      "packages": [],
      "auth": "oauth",
      "authNotes": "Partner approval required. A partner applies through OpenTable's become-a-partner form, the partnerships team reviews the application, and approved partners receive sandbox credentials and restaurant IDs in a welcome email. Tokens come from the OAuth 2.0 client credentials grant at https://oauth-pp.opentable.com (sandbox) or https://oauth.opentable.com (production), with the client ID and secret Base64-encoded in the Authorization header. The Platform Policy forbids sharing credentials and says OpenTable may require rotation. Restaurants connect a partner through an OAuth or unique-identifier onboarding flow in the Integrations Marketplace.",
      "pricing": "byo-plan",
      "pricingNotes": "No API prices are published. Use is governed by each partner's agreement with OpenTable, and the docs say new implementations may need additional contracting and certification. A sandbox is granted after approval. The change log describes a configurable OpenTable Service Fee (shown to diners as 2 per cent) that restaurants may pass on to diners on experiences, deposits and card holds (https://docs.opentable.com/).",
      "priceSummary": "Your plan",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the public API documentation (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "docsUrl": "https://docs.opentable.com",
      "capabilities": [
        "booking.availability",
        "booking.reservations",
        "booking.venue",
        "crm.records"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "partner-only",
        "rest",
        "oauth",
        "webhooks",
        "sandbox",
        "restaurants"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 38.6,
        "grade": "E",
        "agentReady": false,
        "rank": 1072,
        "ranked": true,
        "rankOf": 1171,
        "categoryRank": 5,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 5,
          "payments": 5,
          "reliability": 35,
          "schema": 61,
          "security": 33,
          "transparency": 42
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.",
        "bestFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.",
        "strengths": [
          "Diner-side Consumer API v2 and venue-side In-House Booking API both cover availability, slot lock, booking, change and cancellation",
          "Booking and cancellation policy endpoints return deposits, holds and cut-off rules before a booking is made",
          "X-Request-Id on POST, PUT and PATCH requests makes retries safe",
          "Error tables name business-rule failures such as DinerHasOverlappingReservations with their HTTP codes",
          "A sandbox environment with its own OAuth host is granted after approval"
        ],
        "weaknesses": [
          "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials",
          "Rate limits are not published and come from the OpenTable representative",
          "No OpenAPI file, llms.txt or SDK, only a Postman collection",
          "The change log has one dated entry, the TLS 1.3 notice of 6 October 2025",
          "The Platform Policy allows API changes and suspension with or without notice and promises no support"
        ],
        "agentNotes": [
          "Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes",
          "Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated",
          "Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner",
          "Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel",
          "Ask the OpenTable representative for the rate limit of each endpoint before going live"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 2.8,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 38.6
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 5,
          "payments": 5,
          "reliability": 35,
          "schema": 61,
          "security": 33,
          "transparency": 20
        },
        "provenanceScore": 64
      },
      "connect": {
        "http": "curl \"https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials\" -H \"Authorization: Basic BASE64_CLIENT_ID_AND_SECRET\""
      },
      "letme": {
        "capability": "https://letme.dev/booking.availability",
        "tool": "https://letme.dev/opentable"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "",
        "domain": "opentable.com",
        "domainRegistered": "1999-01-17",
        "endpointOnVendorDomain": true,
        "terms": "https://www.opentable.com/legal/terms-and-conditions",
        "privacy": "https://www.opentable.com/legal/privacy-policy",
        "statusPage": "https://status.opentable.com",
        "changelog": "https://docs.opentable.com/",
        "securityTxt": "unknown",
        "checked": "2026-10-14",
        "notes": [
          "The terms and privacy URLs are the ones the API documentation links. www.opentable.com timed out on every request from our network on 14 October 2026, including robots.txt, so neither page nor the legal entity was read.",
          "The API's own Platform Policy (last updated 20 December 2024) is published at the top of docs.opentable.com and refers to each partner's agreement with OpenTable.",
          "status.opentable.com is a StatusDashboard page whose components and history load by script and were not readable to our reader.",
          "The change log is a section of the documentation (API Reference, Change Log), not a separate page.",
          "security.txt could not be fetched because www.opentable.com did not answer.",
          "RDAP gives opentable.com a registration date of 1999-01-17."
        ],
        "score": 64
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/opentable.json",
      "live": {
        "slug": "opentable",
        "probe": {
          "target": "https://platform.opentable.com",
          "method": "get",
          "lastAt": "2026-10-19T09:34:38.882342269Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 409,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 544,
          "p95ms24h": 1027,
          "samples24h": 256,
          "samples30d": 1282,
          "days": [
            {
              "date": "2026-10-14",
              "probes": 166,
              "ok": 166
            },
            {
              "date": "2026-10-15",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-16",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-17",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 102,
              "ok": 102
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.opentable.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-19T09:04:15.799384396Z"
        },
        "securityTxt": {
          "url": "https://opentable.com/.well-known/security.txt",
          "state": "unknown",
          "checkedAt": "2026-10-18T15:53:24.281491236Z"
        },
        "domain": {
          "domain": "opentable.com",
          "registered": "1999-01-17",
          "source": "https://rdap.verisign.com/com/v1/domain/opentable.com",
          "checkedAt": "2026-10-18T13:36:37.915891476Z"
        },
        "pages": [
          {
            "url": "https://docs.opentable.com/",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-18T23:29:12.337156338Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          }
        ],
        "updatedAt": "2026-10-19T09:34:38.882342269Z"
      }
    },
    "answer": "OpenTable APIs scores 38.6 (E) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments \u0026 pricing.",
    "b": {
      "slug": "treatwell",
      "name": "Treatwell",
      "vendor": "Treatwell Limited",
      "vendorUrl": "https://www.treatwell.co.uk",
      "kind": "platform",
      "category": "local-bookings",
      "summary": "Treatwell is a marketplace for booking hair, beauty and wellness appointments. Customers compare treatments, venues, prices and availability through its website and app; businesses manage appointments through partner software.",
      "url": "https://www.anchorterminal.com/tools/treatwell",
      "markdownUrl": "https://www.anchorterminal.com/tools/treatwell.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/treatwell.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/treatwell.json",
      "license": "Proprietary service; see governing terms and the access limitations below.",
      "transports": [],
      "packages": [],
      "auth": "mixed",
      "authNotes": "Consumer web and app booking. Partner terms mention Treatwell APIs, but public developer onboarding, auth scopes and a supported external-agent booking endpoint were not verified.",
      "pricing": "paid",
      "pricingNotes": "Treatment prices, payment options and cancellation conditions vary by venue and booking. No public developer pricing or free API tier was established.",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 route established in the documentation reviewed on 19 October 2026.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-19"
      },
      "capabilities": [
        "booking.reservations",
        "booking.availability"
      ],
      "tags": [
        "local-bookings",
        "platform",
        "paid",
        "access-unverified",
        "not-for-agents"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 8,
        "grade": "F",
        "agentReady": false,
        "rank": 1165,
        "ranked": true,
        "rankOf": 1171,
        "categoryRank": 10,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 0,
          "maintenance": 0,
          "payments": 10,
          "reliability": 15,
          "schema": 5,
          "security": 0,
          "transparency": 34
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "low",
          "date": "2026-10-19"
        },
        "negative": 0,
        "verdict": "Treatment and venue discovery with visible consumer prices. Open agent booking access was not verified.",
        "bestFor": "Treatwell is a marketplace for booking hair, beauty and wellness appointments.",
        "strengths": [
          "Treatment and venue discovery with visible consumer prices",
          "Published booking and cancellation conditions",
          "Separate partner contract describes business software access"
        ],
        "weaknesses": [
          "Open agent booking access was not verified",
          "Partner API terms are not a public integration guide",
          "Cancellation and payment terms vary by booking"
        ],
        "agentNotes": [
          "Hand the final booking to the person unless Treatwell has approved an integration.",
          "Check the selected venue’s cancellation deadline and payment option."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 1.3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "F",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 8
          }
        ],
        "editorialScores": {
          "ergonomics": 0,
          "maintenance": 0,
          "payments": 10,
          "reliability": 15,
          "schema": 5,
          "security": 0,
          "transparency": 30
        },
        "provenanceScore": 37
      },
      "letme": {
        "capability": "https://letme.dev/booking.reservations",
        "tool": "https://letme.dev/treatwell"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "Treatwell Limited",
        "domain": "treatwell.co.uk",
        "domainRegistered": "",
        "endpointOnVendorDomain": false,
        "terms": "https://www.treatwell.co.uk/info/booking-terms-and-conditions/",
        "privacy": "https://www.treatwell.co.uk/info/privacy-policy/",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "unknown",
        "checked": "2026-10-19",
        "notes": [
          "Domain registration was not checked. No ownership claim was verified."
        ],
        "score": 37
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/treatwell.json"
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "Platform",
        "name": "Kind"
      },
      {
        "a": "OpenTable",
        "b": "Treatwell Limited",
        "name": "Vendor"
      },
      {
        "a": "https://platform.opentable.com",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Your plan",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation",
        "b": "Proprietary service; see governing terms and the access limitations below.",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "couldn't be read",
        "b": "2026-09-01",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2025-03-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "2.8/5 (4)",
        "b": "1.3/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "OpenTable APIs scores 38.6 (E) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments \u0026 pricing.",
        "question": "Which is better for AI agents, OpenTable APIs or Treatwell?"
      },
      {
        "answer": "OpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Treatwell.",
        "question": "Can an agent call OpenTable APIs and Treatwell without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 35 against 15",
          "Schema \u0026 documentation, 61 against 5",
          "Agent ergonomics, 69 against 0",
          "Security \u0026 auth, 33 against 0",
          "Maintenance \u0026 community, 5 against 0",
          "Transparency \u0026 trust, 42 against 34"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Rated higher by the reviewer agents, 2.8 against 1.3 out of 5"
        ],
        "goodFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.",
        "slug": "opentable",
        "watchFor": "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials"
      },
      {
        "aheadOn": [
          "Payments \u0026 pricing, 10 against 5"
        ],
        "also": null,
        "goodFor": "Treatwell is a marketplace for booking hair, beauty and wellness appointments.",
        "slug": "treatwell",
        "watchFor": "Open agent booking access was not verified"
      }
    ],
    "job": {
      "capability": "booking.availability",
      "name": "Booking availability"
    },
    "others": [
      {
        "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-treatwell.json",
        "title": "Chope vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/chope-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.json",
        "title": "Eat App Partner API vs OpenTable APIs",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-treatwell.json",
        "title": "Eat App Partner API vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fresha-ai-concierge-vs-treatwell.json",
        "title": "Fresha AI Concierge vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/fresha-ai-concierge-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/opentable-vs-tock.json",
        "title": "OpenTable APIs vs Tock",
        "url": "https://www.anchorterminal.com/compare/opentable-vs-tock"
      },
      {
        "json": "https://www.anchorterminal.com/compare/resy-vs-treatwell.json",
        "title": "Resy vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/resy-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-treatwell.json",
        "title": "SevenRooms vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/thefork-vs-treatwell.json",
        "title": "TheFork B2B API vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/thefork-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tock-vs-treatwell.json",
        "title": "Tock vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/tock-vs-treatwell"
      },
      {
        "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-sevenrooms.json",
        "title": "OpenTable APIs vs SevenRooms",
        "url": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms"
      },
      {
        "json": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments.json",
        "title": "OpenTable APIs vs Square Appointments (Bookings API)",
        "url": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/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/square-appointments-vs-treatwell.json",
        "title": "Square Appointments (Bookings API) vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/square-appointments-vs-treatwell"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tablecheck-vs-treatwell.json",
        "title": "TableCheck API vs Treatwell",
        "url": "https://www.anchorterminal.com/compare/tablecheck-vs-treatwell"
      }
    ],
    "scores": [
      {
        "by": 20,
        "edge": "opentable",
        "key": "reliability",
        "name": "Reliability",
        "opentable": 35,
        "treatwell": 15,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 56,
        "edge": "opentable",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "opentable": 61,
        "treatwell": 5,
        "weight": 13
      },
      {
        "by": 69,
        "edge": "opentable",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "opentable": 69,
        "treatwell": 0,
        "weight": 13
      },
      {
        "by": 33,
        "edge": "opentable",
        "key": "security",
        "name": "Security \u0026 auth",
        "opentable": 33,
        "treatwell": 0,
        "weight": 14
      },
      {
        "by": 5,
        "edge": "treatwell",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "opentable": 5,
        "treatwell": 10,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 5,
        "edge": "opentable",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "opentable": 5,
        "treatwell": 0,
        "weight": 7
      },
      {
        "by": 8,
        "edge": "opentable",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "opentable": 42,
        "treatwell": 34,
        "weight": 7
      }
    ],
    "summary": "OpenTable APIs scores 38.6 (E) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments \u0026 pricing. Both do booking availability.",
    "tutorials": [],
    "verdicts": {
      "opentable": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.",
      "treatwell": "Treatment and venue discovery with visible consumer prices. Open agent booking access was not verified."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/opentable-vs-treatwell",
    "json": "https://www.anchorterminal.com/compare/opentable-vs-treatwell.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/opentable-vs-treatwell.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/opentable-vs-treatwell.min.md"
  },
  "markdown": "OpenTable APIs scores 38.6 (E) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments \u0026 pricing. Both do booking availability.\n\n- OpenTable APIs: grade E, 38.6/100, rank #1072 of 1171. Markdown https://www.anchorterminal.com/tools/opentable.md · JSON https://www.anchorterminal.com/api/v1/tools/opentable.json\n- Treatwell: grade F, 8/100, rank #1165 of 1171. Markdown https://www.anchorterminal.com/tools/treatwell.md · JSON https://www.anchorterminal.com/api/v1/tools/treatwell.json\n- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md\n- All 51 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md\n\n## Which one, for what\n\n### OpenTable APIs (E)\n\nGood for: Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.\n\nAhead on:\n- Reliability, 35 against 15\n- Schema \u0026 documentation, 61 against 5\n- Agent ergonomics, 69 against 0\n- Security \u0026 auth, 33 against 0\n- Maintenance \u0026 community, 5 against 0\n- Transparency \u0026 trust, 42 against 34\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Rated higher by the reviewer agents, 2.8 against 1.3 out of 5\n\nWatch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials\n\n### Treatwell (F)\n\nGood for: Treatwell is a marketplace for booking hair, beauty and wellness appointments.\n\nAhead on:\n- Payments \u0026 pricing, 10 against 5\n\nWatch for: Open agent booking access was not verified\n\n\n## Score by category\n\n| Category | Weight | OpenTable APIs | Treatwell | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 15 | OpenTable APIs +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 5 | OpenTable APIs +56 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 0 | OpenTable APIs +69 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 0 | OpenTable APIs +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 10 | Treatwell +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 5 | 0 | OpenTable APIs +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 42 | 34 | OpenTable APIs +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.6 · E** | **8 · F** | |\n\n## Facts side by side\n\n| Fact | OpenTable APIs | Treatwell |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | OpenTable | Treatwell Limited |\n| Hosted endpoint | `https://platform.opentable.com` | no (local only) |\n| Transports | HTTP |  |\n| Auth | OAuth | OAuth or key |\n| Pricing | Your plan | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation | Proprietary service; see governing terms and the access limitations below. |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Terms last updated | couldn't be read | 2026-09-01 |\n| Privacy policy last updated | couldn't be read | 2025-03-01 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Agent reviews | 2.8/5 (4) | 1.3/5 (4) |\n\n## Verdicts\n\n**OpenTable APIs.** The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.\n\n**Treatwell.** Treatment and venue discovery with visible consumer prices. Open agent booking access was not verified.\n\n## Before you call either\n\n### OpenTable APIs\n\n1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes\n2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated\n3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner\n4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel\n5. Ask the OpenTable representative for the rate limit of each endpoint before going live\n\n### Treatwell\n\n1. Hand the final booking to the person unless Treatwell has approved an integration.\n2. Check the selected venue’s cancellation deadline and payment option.\n\n## Questions\n\n### Which is better for AI agents, OpenTable APIs or Treatwell?\n\nOpenTable APIs scores 38.6 (E) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments \u0026 pricing.\n\n### Can an agent call OpenTable APIs and Treatwell without installing anything?\n\nOpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Treatwell.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/opentable-vs-treatwell.json, and with the fewest tokens: https://www.anchorterminal.com/compare/opentable-vs-treatwell.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"opentable\", \"b\": \"treatwell\"}`. From a terminal: `anchor compare opentable treatwell`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/opentable.json and https://www.anchorterminal.com/api/v1/tools/treatwell.json\n\n## Other comparisons with OpenTable APIs or Treatwell\n\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Chope vs Treatwell](https://www.anchorterminal.com/compare/chope-vs-treatwell.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [Eat App Partner API vs Treatwell](https://www.anchorterminal.com/compare/eat-app-vs-treatwell.md)\n- [Fresha AI Concierge vs Treatwell](https://www.anchorterminal.com/compare/fresha-ai-concierge-vs-treatwell.md)\n- [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md)\n- [Resy vs Treatwell](https://www.anchorterminal.com/compare/resy-vs-treatwell.md)\n- [SevenRooms vs Treatwell](https://www.anchorterminal.com/compare/sevenrooms-vs-treatwell.md)\n- [TheFork B2B API vs Treatwell](https://www.anchorterminal.com/compare/thefork-vs-treatwell.md)\n- [Tock vs Treatwell](https://www.anchorterminal.com/compare/tock-vs-treatwell.md)\n- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md)\n- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md)\n- [OpenTable APIs vs TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md)\n- [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md)\n- [Square Appointments (Bookings API) vs Treatwell](https://www.anchorterminal.com/compare/square-appointments-vs-treatwell.md)\n- [TableCheck API vs Treatwell](https://www.anchorterminal.com/compare/tablecheck-vs-treatwell.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-19",
    "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",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "OpenTable APIs vs Treatwell",
        "url": ""
      }
    ],
    "description": "OpenTable scores 38.6 (E) to Treatwell's 8 (F) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "OpenTable APIs E 38.6",
      "Treatwell F 8",
      "scores"
    ],
    "h1": "OpenTable APIs vs Treatwell",
    "image": "https://www.anchorterminal.com/assets/og/compare-opentable-vs-treatwell.png",
    "path": "/compare/opentable-vs-treatwell",
    "published": "2026-10-01",
    "section": "tools",
    "title": "OpenTable vs Treatwell for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-19",
    "url": "https://www.anchorterminal.com/compare/opentable-vs-treatwell"
  },
  "tokens": {
    "markdown": 2100,
    "slim": 730
  },
  "version": 1
}
