{
  "data": {
    "a": {
      "slug": "eat-app",
      "name": "Eat App Partner API",
      "vendor": "Eat App (EAT APPLICATION DMCC)",
      "vendorUrl": "https://restaurant.eatapp.co",
      "kind": "http-api",
      "category": "local-bookings",
      "summary": "Eat App is a restaurant reservation and table management system. Its Partner API lets booking channels check availability and create, change and cancel reservations, a Concierge API serves restaurant groups, and a read-only Restaurant MCP server connects AI assistants.",
      "url": "https://www.anchorterminal.com/tools/eat-app",
      "markdownUrl": "https://www.anchorterminal.com/tools/eat-app.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/eat-app.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/eat-app.json",
      "license": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.eatapp.co/partners/v2",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Partner approval required for the Partner API. A booking channel asks to become a partner (info@eatapp.co), Eat App activates partnerships restaurant by restaurant, and its support team issues a long-term API key sent as a Bearer token. A login endpoint also exchanges the partner's email and password for a 24-hour token. Concierge API keys are created by Eat App for restaurant groups. The Restaurant MCP server uses OAuth with dynamic client registration, PKCE and a single `mcp` scope, and the restaurant signs in with its Eat App login.",
      "pricing": "paid",
      "pricingNotes": "No per-call price. The pricing page marks API access in the Enterprise column only (Let's talk) and lists API and webhooks access as an add-on. Table management plans are $99, $199 and $389 a month, or $69, $159 and $299 billed yearly, with a 14-day trial and a $0 plan limited to 100 guests a month. The Restaurant MCP needs an active table management subscription. A sandbox host (api.eat-sandbox.co) is given to partners (https://restaurant.eatapp.co/pricing).",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Partner or Concierge API docs, the MCP guide or the pricing page (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "docsUrl": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4",
      "capabilities": [
        "booking.reservations",
        "booking.availability",
        "booking.venue",
        "crm.records",
        "events.webhooks-send"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "partner-only",
        "rest",
        "mcp",
        "oauth",
        "sandbox",
        "status-page",
        "webhooks",
        "restaurants"
      ],
      "lastRelease": "2026-10-13",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 53.4,
        "grade": "D",
        "agentReady": false,
        "rank": 752,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 3,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 40,
          "payments": 15,
          "reliability": 78,
          "schema": 59,
          "security": 43,
          "transparency": 52
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.",
        "bestFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.",
        "strengths": [
          "idempotency_token on Create Reservation returns the first success for a repeated request",
          "60 requests a minute stated, with a documented 429 body",
          "Better Stack status page with separate Partner API and Concierge API components and incident history",
          "Dated API changelog, latest entry 13 October 2026",
          "Restaurant MCP server with OAuth dynamic client registration and read-only access"
        ],
        "weaknesses": [
          "A booking channel can book only at restaurants whose partnership Eat App has activated",
          "API access sits in the Enterprise column of the pricing page, priced through sales",
          "No OpenAPI file, llms.txt or SDK, only Postman collections",
          "A login endpoint accepts the partner's email and password for a 24-hour token",
          "No security.txt, and the trust centre content did not load for our reader"
        ],
        "agentNotes": [
          "Send a unique idempotency_token with each new booking so a retry returns the first result",
          "Use POST /partners/v2/availability/range, not the legacy availability endpoint",
          "Keep include_tables ranges to 24 hours or less and pass covers with it",
          "Stay under 60 requests a minute and wait for the next minute after a 429",
          "Cancel by PATCH with status canceled, after which the reservation can no longer change"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 53.4
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 40,
          "payments": 15,
          "reliability": 78,
          "schema": 59,
          "security": 43,
          "transparency": 32
        },
        "provenanceScore": 71
      },
      "connect": {
        "http": "curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip'"
      },
      "letme": {
        "capability": "https://letme.dev/booking.reservations",
        "tool": "https://letme.dev/eat-app"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "EAT APPLICATION DMCC",
        "domain": "eatapp.co",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://restaurant.eatapp.co/terms",
        "privacy": "https://restaurant.eatapp.co/privacy",
        "statusPage": "https://status.eatapp.co",
        "changelog": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4",
        "securityTxt": "none",
        "checked": "2026-10-14",
        "notes": [
          "The terms of service (effective 10 September 2025) are entered into by EAT APPLICATION DMCC, Jumeirah Lake Towers, Dubai, licence DMCC-164040, and say the agreement also includes one executed with its licensee Swiggy Limited.",
          "The privacy policy names EAT APPLICATION DMCC and covers GDPR rights and a retention statement without fixed periods.",
          "The API changelog is a section of the Partner API Postman documentation.",
          "security.txt returns 404 on eatapp.co, restaurant.eatapp.co and api.eatapp.co. A trust centre at trust.eatapp.co loads by script and showed only its title to our reader.",
          "RDAP for eatapp.co did not answer, so the registration date is not recorded."
        ],
        "score": 71
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/eat-app.json",
      "live": {
        "slug": "eat-app",
        "probe": {
          "target": "https://api.eatapp.co/partners/v2",
          "method": "get",
          "lastAt": "2026-10-14T09:59:44.997706829Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 179,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 175,
          "p95ms24h": 322,
          "samples24h": 20,
          "samples30d": 20,
          "days": [
            {
              "date": "2026-10-14",
              "probes": 20,
              "ok": 20
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.eatapp.co",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-14T08:53:05.16851429Z"
        },
        "updatedAt": "2026-10-14T09:59:44.997706829Z"
      }
    },
    "answer": "Eat App Partner API scores 53.4 (D) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. SevenRooms leads on transparency \u0026 trust.",
    "b": {
      "slug": "sevenrooms",
      "name": "SevenRooms",
      "vendor": "SevenRooms (a DoorDash company)",
      "vendorUrl": "https://sevenrooms.com",
      "kind": "platform",
      "category": "local-bookings",
      "summary": "SevenRooms is a reservation, table management, guest CRM and marketing platform for restaurants, hotels and other hospitality venues, owned by DoorDash. It runs venues' booking widgets and connects to 100+ booking, POS and voice AI partners.",
      "url": "https://www.anchorterminal.com/tools/sevenrooms",
      "markdownUrl": "https://www.anchorterminal.com/tools/sevenrooms.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sevenrooms.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sevenrooms.json",
      "license": "Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements",
      "transports": [],
      "packages": [],
      "auth": "mixed",
      "authNotes": "No public agent access. API documentation at api-docs.sevenrooms.com moved to individually provisioned accounts on 26 February, and new integrators are sent to a partnerships form. The credential type could not be read first-hand, because the reference sits behind that login.",
      "pricing": "paid",
      "pricingNotes": "No prices are published. The pricing page describes packages and asks for a demo (https://sevenrooms.com/pricing/). No free tier or self-serve trial was found.",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on sevenrooms.com or the public part of the API docs (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "docsUrl": "https://api-docs.sevenrooms.com",
      "llmsTxt": "https://api-docs.sevenrooms.com/llms.txt",
      "capabilities": [
        "booking.venue",
        "booking.reservations",
        "booking.availability",
        "crm.records"
      ],
      "tags": [
        "not-for-agents",
        "sales-led",
        "hosted",
        "closed-source",
        "partner-only",
        "status-page",
        "soc2",
        "restaurants"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 17.7,
        "grade": "F",
        "agentReady": false,
        "rank": 1043,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 6,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 0,
          "maintenance": 15,
          "payments": 0,
          "reliability": 40,
          "schema": 5,
          "security": 14,
          "transparency": 58
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.",
        "bestFor": "Hospitality venues and groups that want reservations, CRM and marketing in one system.",
        "strengths": [
          "Statuspage history with a separate API component",
          "Trust centre lists SOC 2, PCI DSS, subprocessors and a responsible disclosure section",
          "Terms and privacy policy carry 2026 update dates and name the legal entity"
        ],
        "weaknesses": [
          "No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account",
          "Venue-side only. Guests have no accounts, so nothing acts for a diner",
          "No published prices, free tier or self-serve trial",
          "One major outage of VMS and widgets on 7 September 2026"
        ],
        "agentNotes": [
          "Don't plan to call SevenRooms from another agent. To book for a diner, use the venue's booking widget with the person, or a booking channel the venue lists",
          "If you work for a venue or vendor, apply through the SevenRooms partnerships form before planning an integration"
        ],
        "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": 17.7
          }
        ],
        "editorialScores": {
          "ergonomics": 0,
          "maintenance": 15,
          "payments": 0,
          "reliability": 40,
          "schema": 5,
          "security": 14,
          "transparency": 40
        },
        "provenanceScore": 75
      },
      "letme": {
        "capability": "https://letme.dev/booking.venue",
        "tool": "https://letme.dev/sevenrooms"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "SEVENROOMS LLC",
        "domain": "sevenrooms.com",
        "domainRegistered": "2007-09-09",
        "endpointOnVendorDomain": true,
        "terms": "https://sevenrooms.com/terms-of-service/",
        "privacy": "https://sevenrooms.com/privacy-policy/",
        "statusPage": "https://status.sevenrooms.com",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-14",
        "notes": [
          "The terms (updated 17 April 2026) and privacy policy (updated 16 June 2026) name SEVENROOMS LLC, a DoorDash Inc. company.",
          "sevenrooms.com/.well-known/security.txt returns 404. The trust centre at trust.sevenrooms.com (SafeBase) lists a responsible disclosure section.",
          "No public changelog was found. The API docs landing page says it was last updated about six months ago.",
          "RDAP gives sevenrooms.com a registration date of 2007-09-09."
        ],
        "score": 75
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/sevenrooms.json",
      "live": {
        "slug": "sevenrooms",
        "vendorStatus": {
          "page": "https://status.sevenrooms.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-14T09:53:25.49736571Z"
        },
        "updatedAt": "2026-10-14T09:53:25.49736571Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "Platform",
        "name": "Kind"
      },
      {
        "a": "Eat App (EAT APPLICATION DMCC)",
        "b": "SevenRooms (a DoorDash company)",
        "name": "Vendor"
      },
      {
        "a": "https://api.eatapp.co/partners/v2",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements",
        "b": "Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements",
        "name": "Licence"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-13",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2025-09-10",
        "b": "2026-04-17",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-06-16",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Eat App Partner API scores 53.4 (D) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. SevenRooms leads on transparency \u0026 trust.",
        "question": "Which is better for AI agents, Eat App Partner API or SevenRooms?"
      },
      {
        "answer": "Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for SevenRooms.",
        "question": "Can an agent call Eat App Partner API and SevenRooms without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 78 against 40",
          "Schema \u0026 documentation, 59 against 5",
          "Agent ergonomics, 66 against 0",
          "Security \u0026 auth, 43 against 14",
          "Payments \u0026 pricing, 15 against 0",
          "Maintenance \u0026 community, 40 against 15"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.",
        "slug": "eat-app",
        "watchFor": "A booking channel can book only at restaurants whose partnership Eat App has activated"
      },
      {
        "aheadOn": [
          "Transparency \u0026 trust, 58 against 52"
        ],
        "also": null,
        "goodFor": "Hospitality venues and groups that want reservations, CRM and marketing in one system.",
        "slug": "sevenrooms",
        "watchFor": "No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account"
      }
    ],
    "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-sevenrooms.json",
        "title": "Chope vs SevenRooms",
        "url": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-opentable.json",
        "title": "Eat App Partner API vs OpenTable APIs",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-resy.json",
        "title": "Eat App Partner API vs Resy",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-resy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json",
        "title": "Eat App Partner API vs TableCheck API",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-thefork.json",
        "title": "Eat App Partner API vs TheFork B2B API",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-thefork"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-tock.json",
        "title": "Eat App Partner API vs Tock",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-tock"
      },
      {
        "json": "https://www.anchorterminal.com/compare/resy-vs-sevenrooms.json",
        "title": "Resy vs SevenRooms",
        "url": "https://www.anchorterminal.com/compare/resy-vs-sevenrooms"
      },
      {
        "json": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.json",
        "title": "Eat App Partner API vs Square Appointments (Bookings API)",
        "url": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments"
      },
      {
        "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/sevenrooms-vs-square-appointments.json",
        "title": "SevenRooms vs Square Appointments (Bookings API)",
        "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.json",
        "title": "SevenRooms vs TableCheck API",
        "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck"
      },
      {
        "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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock.json",
        "title": "SevenRooms vs Tock",
        "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock"
      }
    ],
    "scores": [
      {
        "by": 38,
        "eat-app": 78,
        "edge": "eat-app",
        "key": "reliability",
        "name": "Reliability",
        "sevenrooms": 40,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 54,
        "eat-app": 59,
        "edge": "eat-app",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "sevenrooms": 5,
        "weight": 13
      },
      {
        "by": 66,
        "eat-app": 66,
        "edge": "eat-app",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "sevenrooms": 0,
        "weight": 13
      },
      {
        "by": 29,
        "eat-app": 43,
        "edge": "eat-app",
        "key": "security",
        "name": "Security \u0026 auth",
        "sevenrooms": 14,
        "weight": 14
      },
      {
        "by": 15,
        "eat-app": 15,
        "edge": "eat-app",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "sevenrooms": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 25,
        "eat-app": 40,
        "edge": "eat-app",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "sevenrooms": 15,
        "weight": 7
      },
      {
        "by": 6,
        "eat-app": 52,
        "edge": "sevenrooms",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "sevenrooms": 58,
        "weight": 7
      }
    ],
    "summary": "Eat App Partner API scores 53.4 (D) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. SevenRooms leads on transparency \u0026 trust. Both do restaurant reservations.",
    "verdicts": {
      "eat-app": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.",
      "sevenrooms": "SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms",
    "json": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.md",
    "slim": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.min.md"
  },
  "markdown": "Eat App Partner API scores 53.4 (D) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. SevenRooms leads on transparency \u0026 trust. Both do restaurant reservations.\n\n- Eat App Partner API: grade D, 53.4/100, rank #752 of 1076. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json\n- SevenRooms: grade F, 17.7/100, rank #1043 of 1076. Markdown https://www.anchorterminal.com/tools/sevenrooms.md · JSON https://www.anchorterminal.com/api/v1/tools/sevenrooms.json\n- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md\n- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md\n\n## Which one, for what\n\n### Eat App Partner API (D)\n\nGood for: Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.\n\nAhead on:\n- Reliability, 78 against 40\n- Schema \u0026 documentation, 59 against 5\n- Agent ergonomics, 66 against 0\n- Security \u0026 auth, 43 against 14\n- Payments \u0026 pricing, 15 against 0\n- Maintenance \u0026 community, 40 against 15\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\n\n### SevenRooms (F)\n\nGood for: Hospitality venues and groups that want reservations, CRM and marketing in one system.\n\nAhead on:\n- Transparency \u0026 trust, 58 against 52\n\nWatch for: No public API or MCP server an outside agent can call. The API reference needs an individually provisioned account\n\n\n## Score by category\n\n| Category | Weight | Eat App Partner API | SevenRooms | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 40 | Eat App Partner API +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 5 | Eat App Partner API +54 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 0 | Eat App Partner API +66 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 14 | Eat App Partner API +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 0 | Eat App Partner API +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 15 | Eat App Partner API +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 58 | SevenRooms +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53.4 · D** | **17.7 · F** | |\n\n## Facts side by side\n\n| Fact | Eat App Partner API | SevenRooms |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | Eat App (EAT APPLICATION DMCC) | SevenRooms (a DoorDash company) |\n| Hosted endpoint | `https://api.eatapp.co/partners/v2` | no (local only) |\n| Transports | HTTP |  |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service under the SevenRooms Terms of Service (updated 17 April 2026) and venue agreements |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-13 | none |\n| Terms last updated | 2025-09-10 | 2026-04-17 |\n| Privacy policy last updated | no date given | 2026-06-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## Verdicts\n\n**Eat App Partner API.** A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.\n\n**SevenRooms.** SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.\n\n## Before you call either\n\n### Eat App Partner API\n\n1. Send a unique idempotency_token with each new booking so a retry returns the first result\n2. Use POST /partners/v2/availability/range, not the legacy availability endpoint\n3. Keep include_tables ranges to 24 hours or less and pass covers with it\n4. Stay under 60 requests a minute and wait for the next minute after a 429\n5. Cancel by PATCH with status canceled, after which the reservation can no longer change\n\n### SevenRooms\n\n1. Don't plan to call SevenRooms from another agent. To book for a diner, use the venue's booking widget with the person, or a booking channel the venue lists\n2. If you work for a venue or vendor, apply through the SevenRooms partnerships form before planning an integration\n\n## Questions\n\n### Which is better for AI agents, Eat App Partner API or SevenRooms?\n\nEat App Partner API scores 53.4 (D) on agent readiness against SevenRooms's 17.7 (F), and leads in 6 of 7 scored categories. SevenRooms leads on transparency \u0026 trust.\n\n### Can an agent call Eat App Partner API and SevenRooms without installing anything?\n\nEat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for SevenRooms.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-app\", \"b\": \"sevenrooms\"}`. From a terminal: `anchor compare eat-app sevenrooms`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-app.json and https://www.anchorterminal.com/api/v1/tools/sevenrooms.json\n\n## Other comparisons with Eat App Partner API or SevenRooms\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md)\n- [Eat App Partner API vs TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Eat App Partner API vs Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.md)\n- [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md)\n- [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md)\n- [SevenRooms vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments.md)\n- [SevenRooms vs TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.md)\n- [SevenRooms vs TheFork B2B API](https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.md)\n- [SevenRooms vs Tock](https://www.anchorterminal.com/compare/sevenrooms-vs-tock.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-14",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Eat App Partner API vs SevenRooms",
        "url": ""
      }
    ],
    "description": "Eat App Partner scores 53.4 (D) to SevenRooms's 17.7 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Eat App Partner API D 53.4",
      "SevenRooms F 17.7",
      "scores"
    ],
    "h1": "Eat App Partner API vs SevenRooms",
    "image": "https://www.anchorterminal.com/assets/og/compare-eat-app-vs-sevenrooms.png",
    "path": "/compare/eat-app-vs-sevenrooms",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Eat App Partner vs SevenRooms for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms"
  },
  "tokens": {
    "markdown": 2100,
    "slim": 730
  },
  "version": 1
}
