# Resy > 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. - Canonical: https://www.anchorterminal.com/tools/resy - Markdown: https://www.anchorterminal.com/tools/resy.md (~4,200 tokens) - Slim: https://www.anchorterminal.com/tools/resy.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/resy.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-14 ## Overview **Grade F · 10.3/100 · rank #1068 of 1076 · #9 in Restaurant & local bookings · not agent-ready · not for agents · confidence low** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Resy (American Express) (https://resy.com) | | Kind | Platform | | Category | Restaurant & local bookings (https://www.anchorterminal.com/categories/local-bookings) | | Auth | OAuth · 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 (Paid) · 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. | | x402 | No · No x402, MPP or L402 on resy.com/join or the MCP endpoint's OAuth metadata (checked 2026-10-14). | | Licence | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock | | llms.txt | not found | | Surface listed | Resy, read from resy.com/join and its integrations and platform security pages, the Resy blog, and the OAuth metadata of the Amex dining MCP endpoint on 14 October 2026. No account was created and no MCP tool was called | | Diner or venue | Both, for people. The app and website book for diners. Resy OS runs venues | | Outside agent access | None in public. A partner-only MCP endpoint exists under American Express's API gateway, with pre-registered OAuth clients only | | Related listing | Tock, now part of the Resy network, keeps its own dashboard, terms and privacy policy (see the tock listing) | | Company | Resy Network, Inc., owned by American Express (https://resy.com/join/integrations/ footer) | | Capabilities | booking.reservations, booking.availability, booking.venue | | Tags | not-for-agents, sales-led, hosted, closed-source, partner-only, ios, android, restaurants | | JSON | https://www.anchorterminal.com/api/v1/tools/resy.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-14 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 25 | 5.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 0 | 0.0 | | Agent ergonomics | 13% | 16.2 | 0 | 0.0 | | Security & auth | 14% | 17.5 | 3 | 0.5 | | Payments & pricing | 10% | 12.5 | 0 | 0.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 25 | 2.2 | | Transparency & trust (editorial 8, provenance 52) | 7% | 8.8 | 30 | 2.6 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **10.3 → F** | ### Why each score - Reliability 25: Read with the hosted lines. status.resy.com exists but loads by script and showed no components to our reader (10 of 20). No readable history (5). No published limits or retry guidance for an outside agent (0, 0). No SLA (0). The service is not labelled beta (10). Total 25. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 0: Graded on the interface an outside agent can use. No public API, documentation or llms.txt was found. The Amex dining MCP endpoint publishes only OAuth metadata and accepts pre-registered clients, so there is no public contract to read (0 on every line). This says nothing about the service for diners. - Agent ergonomics 0: Graded on the interface an outside agent can use. With none in public, every line scores nothing (0). This says nothing about the app for people. - Security & auth 3: Graded on the interface an outside agent can use. With none in public, the credential, least-privilege, injection and audit lines score nothing (0 of 30, 0 of 20, 0 of 15, 0 of 15). The security programme line is scored. The platform security page describes encryption, access controls and a fraud team, without a named certification, disclosure policy or bug bounty. resy.com serves its app page for /.well-known/security.txt rather than a file (3 of 20). Total 3. - Payments & pricing 0: Read with the hosted rule. No x402, MPP or L402 (0). No venue or API prices found, and diner pages could not be read (0). No free tier confirmed (0). Access is through sales or the app (0). Total 0. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 25: Read for a closed service. Resy added Tock's venues on 11 August 2026, a dated product change within 90 days (20). Fewer than three dated changes found (0). The platform security page names chat, email and self-service support, untested (5 of 15). No public SDK (0). No package to judge (0). Total 25. - Transparency & trust 30: Closed service. The terms and privacy policy on resy.com render by script and were not read, so only the footer's entity name is confirmed (5 of 30). The platform security page says data is destroyed or de-identified when no longer needed, with no periods (3 of 30). No deprecation policy found (0). No subprocessors found (0). Total 8. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/resy.md (JSON https://www.anchorterminal.com/fixes/resy.json) ### What we couldn't check - unchecked: Resy's terms of service, privacy policy and security.txt, because resy.com renders by script - unchecked: status.resy.com components and history, which load by script - Which clients American Express has registered for the dining MCP endpoint, and what tools it exposes. No tool list is public and no tool was called - Whether Resy publishes any partner API documentation outside American Express's gateway ### Sources - Resy and Tock announcement: (seen 2026-10-14) - integrations page: (seen 2026-10-14) - platform security page: (seen 2026-10-14) - MCP protected-resource metadata: (seen 2026-10-14) - MCP authorisation server metadata: (seen 2026-10-14) ## Who's behind it (provenance 52/100, checked 2026-10-14) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Resy Network, Inc. | 20/20 | | Domain age | resy.com, registered 2001-11-14 (24 years) | 15/15 | | Endpoint on the vendor's domain | is not on resy.com | 0/15 | | Terms of service | not found | 0/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | status.resy.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0. **Privacy policy** (https://resy.com/privacy), read 2026-10-14. Our reader couldn't read it (the page has 10 words of text without a browser, so the document is drawn by script or sits elsewhere). ## Live (updated 2026-10-14 08:53 UTC) - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/resy.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 1. 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 2. Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | TableCheck API | C | 57.1 | 661 | booking.availability, booking.reservations, booking.venue | no | https://www.anchorterminal.com/tools/tablecheck.md | | Eat App Partner API | D | 53.4 | 752 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/eat-app.md | | TheFork B2B API | E | 43.6 | 951 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/thefork.md | | OpenTable APIs | E | 38.6 | 994 | booking.availability, booking.reservations, booking.venue | no | https://www.anchorterminal.com/tools/opentable.md | | SevenRooms | F | 17.7 | 1043 | booking.venue, booking.reservations, booking.availability | no | https://www.anchorterminal.com/tools/sevenrooms.md | | Square Appointments (Bookings API) | B | 68.1 | 242 | booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/square-appointments.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Resy added Tock's venues to its app on 11 August 2026, and eligible Tock purchases count towards the Resy Credit from 15 September 2026 (source: ) - The MCP endpoint at apigw.americanexpress.com/dining/v1/mcp returns 401 with a resource metadata link naming the scope 600003928_DINING_RESY_MCP_APPS (source: ) - The authorisation server accepts the authorisation code and client credentials grants with client_secret_jwt only, and has no dynamic registration endpoint (source: ) - Resy says its platform security team blocked over 830 million instances of bot traffic in the first quarter of 2025 and supports laws against unauthorised reservation resale (source: ) - The integrations page names POS, discovery, CRM and analytics partner categories without public API documentation (source: ) - #9 of 9 in Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md - All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md ## Compare - [Chope vs Resy](https://www.anchorterminal.com/compare/chope-vs-resy.md): F 13.3 vs F 10.3 - [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md): D 53.4 vs F 10.3 - [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md): F 10.3 vs F 17.7 - [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md): F 10.3 vs C 57.1 - [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md): F 10.3 vs E 43.6 - [Resy vs Tock](https://www.anchorterminal.com/compare/resy-vs-tock.md): F 10.3 vs F 12.4 - [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md): E 38.6 vs F 10.3 - [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-vs-square-appointments.md): F 10.3 vs B 68.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on resy.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "resy", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Resy on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Resy on Anchor Terminal](https://www.anchorterminal.com/badges/resy.svg)](https://www.anchorterminal.com/tools/resy) ``` Plain link: ```html Resy on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Resy is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/resy-dark.png - Light: https://www.anchorterminal.com/assets/share/resy-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=resy