# Agentic Reservations — Resy Restaurant Booking via x402

> Agentic Reservations — Resy Restaurant Booking via x402 is a paid API for AI agents from agentres.dev, paid per call via x402, $3/call, status unknown (last checked 2026-09-14).

Creates a restaurant reservation booking job on Resy for a specified venue, date, party size, and drop time, paid via USDC crypto wallet

## Facts

- Endpoint: POST https://agentres.dev/api/reservation-jobs/create
- Price: $3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentic-reservations-resy-restaurant-booking-via-x402-5d93bc76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_10lpqncmBpqLGLsBPH7Zl

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-resy-restaurant-booking-via-x402-5d93bc76 -d '<json body>'
```

Example prompt: Book me a table for 2 at 4 Charles Prime Rib on August 14th — set the drop time to July 15th at 1pm and pay with my USDC wallet.

## When to prefer this

Use this endpoint when an AI agent needs to autonomously book restaurant reservations on Resy and can pay via USDC crypto (x402 protocol). Prefer this over manual booking flows when automating dining reservations, especially for hard-to-get tables that require precise drop-time scheduling. Best suited for agents with a crypto wallet and a user who wants hands-off restaurant booking.

## Known failure modes

- Insufficient USDC balance in wallet — payment fails and job is not created
- Invalid venue_id — Resy venue not found or not supported
- Requested reservation date or time not available
- Malformed drop_time or reservation_date format
- Missing required fields (venue_id, party_size, reservation_date) — 400 error
- Resy API unavailable or rate-limited — upstream failure

## How this service works

Create a paid reservation job that books a hard-to-get Resy table the moment its booking window opens. Failed or duplicate enqueues are refunded.

## Output

Returns a JSON object with a job_id (UUID), a status field set to 'queued', the venue_id, charge_id for the USDC payment, the scheduled drop_time, party_size, restaurant_name, and reservation_date confirming the booking job was created.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "venue_id": {
   "type": "string",
   "description": "Venue id from /api/reservation-jobs/options. Provide venue_id or restaurant."
  },
  "party_size": {
   "type": "integer",
   "maximum": 20,
   "minimum": 1
  },
  "restaurant": {
   "type": "string",
   "description": "Restaurant name to resolve against the supported list. Provide venue_id or restaurant."
  },
  "preferred_hour": {
   "type": "integer",
   "default": 18,
   "maximum": 23,
   "minimum": 0
  },
  "preferred_minute": {
   "type": "integer",
   "default": 0,
   "maximum": 59,
   "minimum": 0
  },
  "reservation_date": {
   "type": "string",
   "format": "date",
   "description": "Desired reservation date (YYYY-MM-DD)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "job_id": "0a1b2c3d-4e5f-6071-8293-a4b5c6d7e8f9",
  "status": "queued",
  "venue_id": "834",
  "charge_id": "9f8e7d6c-5b4a-3928-1706-f5e4d3c2b1a0",
  "drop_time": "2026-07-15T13:00:00Z",
  "party_size": 2,
  "restaurant_name": "4 Charles Prime Rib",
  "reservation_date": "2026-08-14"
 }
}
```

## More

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