# Agentic Reservations — Restaurant Booking via Resy

> Agentic Reservations — Restaurant Booking via Resy is a paid API for AI agents from agentic-reservations.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Books a restaurant reservation on Resy on behalf of an AI agent, charging $0.10 USDC per successful booking via crypto wallet.

## Facts

- Endpoint: POST https://agentic-reservations.vercel.app/api/book
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentic-reservations-restaurant-booking-via-resy-a5dc149e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gSwAiTpF9LEe-UAjdXom8

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentic-reservations-restaurant-booking-via-resy-a5dc149e -d '<json body>'
```

Example prompt: Can you book me a table for 2 at a cozy Italian restaurant in the West Village this Saturday at 7:30pm — something romantic and not too loud?

## When to prefer this

Use this endpoint when the user explicitly wants to book a restaurant reservation and the venue is likely listed on Resy (popular in major US cities, especially NYC). Prefer this over generic search when the user is ready to commit to a specific time, date, and party size. Ideal for AI agents that need to complete the full booking loop autonomously, including payment, without requiring the user to visit a separate app.

## Known failure modes

- No availability at requested restaurant, date, or time — returns an error or alternative slots
- Restaurant not listed on Resy — endpoint cannot book non-Resy venues
- Invalid or insufficient USDC wallet balance — payment fails and booking is not made
- Ambiguous restaurant name or location — may fail to resolve the correct venue
- Requested party size exceeds available table sizes — booking fails

## How this service works

Book a paid Resy reservation for the authenticated user using a slot config token.

## Output

A reservation confirmation from Resy, including booking ID, confirmed restaurant name, date, time, party size, and any relevant reservation details or instructions provided by the restaurant.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "day": {
   "type": "string",
   "format": "date",
   "description": "Date in YYYY-MM-DD format"
  },
  "venue_id": {
   "type": "string",
   "description": "Resy venue ID"
  },
  "config_id": {
   "type": "string",
   "description": "Slot config token from /api/availability"
  },
  "party_size": {
   "type": "integer",
   "minimum": 1,
   "description": "Number of guests"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentic-reservations-restaurant-booking-via-resy-a5dc149e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentic-reservations.vercel.app](https://www.zero.xyz/host/agentic-reservations.vercel.app/llms.txt)