Spiral gives your agent every tool with one account. Browse the tools →

AlexandriaMaps & ReviewsAvailable now

Resy · Slot conditions

resy-com/restaurants/slot_conditions

Get places and reviews from maps with Resy · Slot conditions from Alexandria through one Spiral API key. After availability or search_venues returned a slot config_token. Alternatively give venue_id + day (+ optional start time and seating type) and the first matching slot of that day is described. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

Pricing

$0.00873 per call.

Limits

Runs
In the background
Returns
json
Longest queue wait
1 hour
Run deadline
5 minutes
Longest run, end to end
225 minutes
Largest inline input
1 MB
Largest input file
2 GB
Largest output
5 GB

Input

FieldKindDefaultDescription
day requiredtext—

Calendar day: YYYY-MM-DD, today, tomorrow or +N days from today. Relative days resolve on the UTC calendar. Pattern: ^([0-9]{4}-[0-9]{2}-[0-9]{2}|today|tomorrow|\+[0-9]{1,3})$.

venue_idnumber
1 to …
—

Resy venue id (id.resy, e.g. 77859).

party_sizenumber
1 to 20
—

Number of guests (default 2).

start_timetext—

With venue_id: pick the slot starting at this venue-local time (default: first slot of the day). Pattern: ^([01][0-9]|2[0-3]):[0-5][0-9]$.

config_tokentext—

Slot token from availability or search_venues. Pattern: ^rgs://resy/[0-9]+/[0-9]+/[0-9]+/[0-9]{4}-[0-9]{2}-[0-9]{2}/[0-9]{4}-[0-9]{2}-[0-9]{2}/[0-9]{2}:[0-9]{2}:[0-9]{2}/[0-9]+/[^/]+$.

seating_typetext—

With venue_id: pick a slot with this seating label (e.g. Counter).

Same request in code

curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "resy-com/restaurants/slot_conditions",
    "input": {
      "day": "<day>"
    }
  }'

Frequently asked questions

How much does Resy · Slot conditions cost?

$0.00873 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.

How do I use Resy · Slot conditions through an API?

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "resy-com/restaurants/slot_conditions"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.

Do I need an account with Alexandria to use Resy · Slot conditions?

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

Can my AI agent use Resy · Slot conditions?

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.