SevenRooms

# Fix list: SevenRooms

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/sevenrooms, the October 2026 research run, assessed 14 October 2026. Grade F, 17.7 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on SevenRooms: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Agent ergonomics, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use. With the reference closed, context cost, pagination, errors, retries and defaults have nothing public to score (0 on each line). This says nothing about the API for approved partners.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 2. Schema & documentation, 5 out of 100, up to 15.4 more on the total

Why it scored 5: Graded on the interface an outside agent can use. The API reference moved behind individually provisioned accounts on 26 February, so the contract, description, typed-input and example lines score nothing in public (0 of 25, 0 of 20, 0 of 15, 0 of 15). An llms.txt exists on the docs site, but it lists only the landing page that explains the login (5 of 10). No public changelog (0 of 15). Total 5.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 3. Security & auth, 14 out of 100, up to 15.1 more on the total

Why it scored 14: 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 SafeBase trust centre lists SOC 2 and PCI DSS and has a responsible disclosure section. sevenrooms.com has no security.txt, and no bug bounty or public advisories were found (14 of 20). Total 14.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Payments & pricing, 0 out of 100, up to 12.5 more on the total

Why it scored 0: Read with the hosted rule. No x402, MPP or L402 (0). The pricing page describes packages without prices and asks for a demo (0). No free tier or self-serve trial found (0). A venue signs up through sales (0). Total 0.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 5. Reliability, 40 out of 100, up to 12 more on the total

Why it scored 40: Read with the hosted lines. status.sevenrooms.com on Statuspage with component history, including an API component (20). In the 90 days to 14 October 2026 the feed shows a minor degradation of API, Booking and Sync on 4 August (19 minutes) and a major partial outage of VMS and widgets on 7 September (about 3 hours 40 minutes), which we read as one major outage (10). No rate limits published, since the API reference is not public (0). No overload or retry guidance found (0). No SLA found (0). The platform is not labelled beta (10). Total 40.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 6. Maintenance & community, 15 out of 100, up to 7.4 more on the total

Why it scored 15: Read for a closed service. No public changelog. The API docs landing page says it was last updated about six months ago, which we take as the latest change, within 180 days (10 of 30). No three dated changes in 90 days (0). api-integration-support@sevenrooms.com for API questions, untested (5 of 15). No public SDK or MCP server (0). No package to judge (0). Total 15.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 58 out of 100, up to 3.7 more on the total

Made of editorial 40, provenance 75.

Why it scored 58: Closed service under dated terms of service, updated 17 April 2026, naming SEVENROOMS LLC (15). The privacy policy, updated 16 June 2026, describes processing for venues and guests and retention for as long as needed for its purposes, without fixed periods (15 of 30). No deprecation policy or dated notices found (0). The trust centre has a subprocessors section and names Google Cloud Platform among its infrastructure entries, though not every entry rendered for our reader (10 of 20). Total 40.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points (5.1 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- The credential model, rate limits and endpoints of the SevenRooms API, which sit behind a provisioned docs login
- Whether the 26 February date on the docs landing page is 2026 or an earlier year. The page gives no year
- Which subprocessors the trust centre names in full. Only part of the list rendered for our reader

## 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

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- 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

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.