# Agentic Reservations — Get Reservation Job Status

> Agentic Reservations — Get Reservation Job Status is a free API for AI agents from agentres.dev, callable via x402, Free, status unknown (last checked 2026-09-13).

Retrieves the status and result of a previously submitted restaurant reservation booking job on Resy

## Facts

- Endpoint: GET https://agentres.dev/api/reservation-jobs/%7Bjob_id%7D
- Price: Free
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentic-reservations-get-reservation-job-status-0008201f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N2irnaiYCKKLgURByQ3wI

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-get-reservation-job-status-0008201f
```

Example prompt: Can you check whether that Resy reservation job I submitted earlier went through? The job ID is 0a1b2c3d-4e5f-6071-8293-a4b5c6d7e8f9 — I want to know if the booking at 4 Charles Prime Rib for August 14th succeeded and whether the payment was processed.

## When to prefer this

Use this endpoint after submitting a reservation booking job to check its outcome. This is the polling/status-check step in the async reservation workflow — call it after receiving a job_id from the booking initiation endpoint. Prefer this over re-submitting a booking when you already have a job_id and just need to know if it succeeded.

## Known failure modes

- Invalid or unknown job_id returns a 404 not found error
- Job still pending returns a status other than 'succeeded' (e.g. 'pending' or 'failed')
- Payment failure results in a failed job status with payment status not 'paid'
- Malformed job_id format returns a 400 bad request
- Network timeout if the polling request takes too long

## How this service works

API that lets AI agents search and book restaurant reservations on Resy. Pay $0.01 USDC per booking with a crypto wallet.

## Output

Returns a JSON object with the job_id, status (e.g. 'succeeded'), payment details (rail, status, amount in cents), the drop_time when the reservation was released, the restaurant name, and the reservation date.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "job_id": "0a1b2c3d-4e5f-6071-8293-a4b5c6d7e8f9",
  "status": "succeeded",
  "payment": {
   "rail": "x402_base_usdc",
   "status": "paid",
   "amount_cents": 300
  },
  "drop_time": "2026-07-15T13:00:00Z",
  "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-get-reservation-job-status-0008201f/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)