Agentic Reservations

Endpoints (20 live)

• GET /api/discover/restaurants/probe — Full detail for one Blackbird-network restaurant: locations with addresses, coordinates, time zone, and live open hours per location. Restaurant id comes from the discovery list endpoint. (0.01 USDC on Base)
• GET /api/wait-times — Live restaurant wait times from camera-based crowd data. One call lists every monitored location with its slug, open status, current crowd count, and wait in minutes. (0.01 USDC on Base)
• POST /api/book — Book a paid Resy reservation for the authenticated user using a slot config token. (0.01 USDC on Base)
• POST /api/account — Fetches account-related data from AgentRes. (0 USDC on Solana)
• GET /api/discover/restaurants — Restaurant recommendations from the Blackbird network (~2,000 curated restaurants, mostly NYC and San Francisco). Full-text search plus city/neighborhood filters, with complete specials on every result, refreshed daily from a cache (never a live call) — e.g. every West Village restaurant with its current Fly-reward offers in one call. (0.01 USDC on Solana)
• GET /api/discover/restaurants/1 — Full detail for one Blackbird-network restaurant: locations with addresses, coordinates, time zone, and live open hours per location. Restaurant id comes from the discovery list endpoint. (0.01 USDC on Solana)
• GET /api/discover/restaurants/1/specials — Cached specials and offers for one Blackbird-network restaurant, refreshed daily by a cron job (never a live call) — e.g. Fly-reward multipliers like 'Earn 10x Fly when you pay with Blackbird'. Restaurant id comes from the discovery list endpoint. (0.01 USDC on Solana)
• POST /api/reservation-jobs/1/refund — Claim the refund for a canceled, failed, or timed-out reservation job. The job id goes in the URL path; no body needed. Idempotent. (0 USDC on Solana)
• POST /api/reservation-jobs/1/cancel — Cancel a queued reservation job. The job id goes in the URL path; no body needed. The paid charge becomes refund-eligible and is claimed via the refund endpoint. (0 USDC on Base)
• GET /api/reservation-jobs/1 — Get a reservation job's status and payment state. The job id goes in the URL path. (0 USDC on Base)
• GET /api/discover/restaurants/:id — Full detail for one Blackbird-network restaurant: locations with addresses, coordinates, time zone, and live open hours per location. Restaurant id comes from the discovery list endpoint. (0.01 USDC on Solana)
• GET /api/me — Check the current agentres account, wallet identity, and whether the user's Resy account is linked. (0 USDC on Base)
• GET /api/reservations — List upcoming or past Resy reservations for the authenticated agentres user. (0 USDC on Base)
• GET /api/reservation-jobs — List the authenticated account's reservation jobs, newest first. (0 USDC on Base)
• GET /api/availability — Find available Resy reservation slots for a venue, party size, and date. (0 USDC on Base)
• GET /api/wait-times/history — Historical restaurant line counts for one monitored location over a time range — raw detection events or 1m/5m/1h bucket aggregates. Useful for questions like when a restaurant is least busy. (0.01 USDC on Solana)
• POST /api/reservation-jobs/create — 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. (3 USDC on Solana)
• POST /api/cancel — Cancel an existing Resy reservation using the reservation token returned by /api/reservations. (0 USDC on Base)
• POST /api/link-resy — Link a user's Resy account by requesting or verifying a Resy email OTP code. (0 USDC on Base)
• GET /api/search — Search Resy restaurants by name and return matching venues with IDs for availability checks. (0 USDC on Base)