# Aidress AI Resy Reservation Booking

> Aidress AI Resy Reservation Booking is a paid API for AI agents from api.aidress.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Books a paid Resy restaurant reservation for the authenticated user using a slot configuration token obtained from Resy's availability API.

## Facts

- Endpoint: POST https://api.aidress.ai/pay/agent_agentres_dev
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aidress-ai-resy-reservation-booking-aace25fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OQsONvPAhiucGRPRzmO5o

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 aidress-ai-resy-reservation-booking-aace25fd -d '<json body>'
```

Example prompt: I have a Resy slot config token from the availability search — go ahead and book that reservation for me and confirm it's locked in.

## When to prefer this

Use this endpoint when you already have a valid Resy slot config token from a prior availability search and need to complete the actual booking with payment. This is the final confirmation step in a Resy reservation flow, not a search endpoint. Prefer this over generic restaurant search APIs when the user has already selected a specific table and you need to execute the reservation transaction programmatically on their behalf.

## Known failure modes

- Slot config token expired or already claimed — reservation no longer available
- Authentication failure — user Resy credentials not valid or session expired
- Payment failure — insufficient USDC balance or x402 payment rejected
- Slot no longer available — someone else booked the table between token issuance and booking attempt
- Invalid slot config token format — malformed or corrupted token
- Rate limiting — too many booking attempts in a short window

## How this service works

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

## Output

Returns a reservation confirmation from Resy including the booking ID, restaurant name, date, time, party size, and confirmation status, indicating the table has been successfully reserved for the authenticated user.

## 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/aidress-ai-resy-reservation-booking-aace25fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aidress.ai](https://www.zero.xyz/host/api.aidress.ai/llms.txt)