resbot connects to your Resy account, arms a booking, and races the moment a venue releases its tables. An always-on worker refreshes auth, polls every ~80ms, holds the slot, and books it — first poll to confirmed in about 1.1 seconds.
No browser automation. No LLM in the hot path. Just the Resy JSON API, hit fast.
The hard part of a hot reservation isn't the booking — it's being there the instant the table appears. resbot is engineered for exactly that moment.
When the venue releases tables, the worker is already polling the find endpoint every ~80ms — no warmup, no missed window.
Your token is AES-256 encrypted at rest, bound to your account, and never shown again. Server-only, never sent to the browser.
Watch every poll, hold, and book event stream in real time as the race runs — the same log the worker writes, as it happens.
Arm a booking once. The always-on worker handles the schedule, the refresh, the race, and the confirmation without you watching.
Measured first-poll-to-confirmation. Find the slot, hold the book_token, commit the reservation — all in about a second.
Direct calls to Resy's JSON API — no headless browser, no flaky automation, no clicking through a UI under time pressure.
Connect once, compose the booking you want, arm it, and let the worker take the drop.
Link your Resy account. Your token is encrypted the moment it lands and used only on the server.
Pick the restaurant, date, party size, time window, and the daily drop time the venue releases tables.
Hand the booking to the worker. It schedules itself against the drop and waits, fully loaded.
At the drop, it refreshes auth, polls, holds, and books — then streams the confirmation back to you live.
Connect your Resy account and let resbot take the next drop for you.
Get started