# Take bookings for a venue as its phone or chat agent

> Take bookings for a venue as its phone or chat agent: 2 companies fully do it, 3 with a limit, 12 carry the tag. Every listing in Restaurant & local bookings with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/local-bookings.venue-booking-agent/
- Markdown: https://www.anchorterminal.com/niches/local-bookings.venue-booking-agent/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/local-bookings.venue-booking-agent/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/local-bookings.venue-booking-agent/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 3 | 12 | 20 | 9 |

## What counts as done

Availability searched and an appointment or reservation created, changed or cancelled in the venue's own calendar through the API, with the venue's no-show and deposit rules applied, on the venue's current plan.

Measured, for our own tests: zero overlapping bookings when two creates for the same slot run at once.

How agents ask for it: answer the salon's calls and book people in; rebook all of Devon's clients, he's off Thursday; let customers book from our own app

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **OpenTable APIs (OpenTable)**: The In-House Booking (Voice AI) API covers availability, booking lock, create with credit-card hold, change, lookup, cancel and status, with X-Request-Id idempotency on writes.
- **TheFork B2B API (La Fourchette SAS)**: Built for AI phone agents: timeslots, create, update and cancel in TheFork Manager, guarantee requests sent to the diner, and 409 DOUBLE_BOOKING on conflicts.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Eat App Partner API (EAT APPLICATION DMCC)**: Availability, create, update, cancel, table_ids that fail with 422 when taken and payment reporting all exist, but the context records API access as an Enterprise or add-on item priced through sales, which this pass did not re-read.
- **Square Appointments (Bookings API) (Block, Inc.)**: Seller-level create, update and cancel work into the live calendar (acc-07), but need Appointments Plus or Premium or return 403, no-show-fee services are excluded, and acc-26 saw concurrent creates both ACCEPTED, below the zero-overlap bar.
- **TableCheck API (TableCheck Inc.)**: Booking v1 serves merchant-owned flows with blockages, amend and cancel, but has no payments support, so deposit rules can't be applied, and POST reservations has no idempotency key.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Resy (Resy Network, Inc.)**: acc-10 reports API keys are issued to venues, but no venue API documentation is public, so endpoints and plan rules could not be read.
- **SevenRooms (SEVENROOMS LLC)**: SevenRooms advertises a booking API and voice partners, but the public docs are an empty index (the llms.txt points to a page with a title only), so endpoints and limits could not be read.

- not this job: Chope (The Chope Group Pte Ltd): No venue API is documented on chope.co.
- not this job: Tock (Tock LLC): No documented write endpoints for a venue's agent; the docs index says docs are coming.
- not this job: Treatwell (Treatwell Limited): No partner API documentation is public; the supplier pages are contract terms, not an integration guide.

## What stops agents finishing

- writes fail with 403 unless the venue pays for a higher plan
- a service with a no-show fee cannot be booked through the API
- each venue runs a different booking platform with its own integration

## Around it

Before: voice-agents.answer-call, messaging.receive-sms. After: messaging.send-confirmation, crm.upsert-contact.

## Where this comes from

Weight 20 of 100 in Restaurant & local bookings: 9 of 30 counted accounts; all but one on Square's developer forum, so the weight leans on one vendor's API

As data: https://www.anchorterminal.com/api/v1/use-cases/local-bookings.venue-booking-agent.json, or the MCP tool get_use_case with id local-bookings.venue-booking-agent. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
