Use SeatSwiper from any AI agent

What it does

The connector gives your agent the same booking abilities as the SeatSwiper dashboard, on your account and with the same safeguards: it can find restaurants, tell you when a date releases, set up a drop race or a cancellation watch, and report results. It races the moment a venue releases its tables across Resy, SevenRooms, and OpenTable — no tab-refreshing at midnight.

Things you can ask once connected:

• “Get me a table for 2 at Don Angie the moment reservations open.”
• “When do reservations for 4 Charles Prime Rib drop, and can you race the next one?”
• “Watch Semma for cancellations this Saturday, party of 4.”
• “What’s my SeatSwiper setup missing before I can book?”
• “List my bookings and cancel the Tatiana one.”

Why it’s safe to hand to an agent

• Your account stays out of trouble. Agents that log in as you and refresh Resy or OpenTable all night are exactly what reservation platforms flag. Through SeatSwiper, your agent sends one request and our engine does the waiting: a drop race works only in the half minute around the release, and cancellation watches check every few minutes, five at most.
• Your agent never holds your logins. It gets an access token or agent key for your SeatSwiper account only — never your Resy, OpenTable, or SevenRooms credentials, and never your card number. We store tokens and keys only as one-way hashes.
• Nothing books without your yes. The booking tool refuses to run until the agent has confirmed the venue, date, party size, time window, and the fee with you.
• Same engine, same guardrails. Agents use the exact booking engine the dashboard uses — card required before arming, the 5-watch limit, and every platform check. Every table is booked in your name; nothing is resold.
• You stay in control. Every connected agent and agent key is listed on your dashboard, and one click cuts it off.

How to connect

Everything starts from the ✦ AI chip at the top of your dashboard. Pick the path your agent supports:

• Claude (easiest). Click Add to Claude — Claude opens with the connector pre-filled; click Add, then Connect. Manual path: Settings → Connectors → Add custom connector → paste https://www.seatswiper.com/api/mcp.
• ChatGPT. Settings → Connectors → Advanced → Developer mode → Add → paste the connector URL.
• Meta Muse. Ask Muse to add a custom connector with the URL https://www.seatswiper.com/api/mcp. When it asks for a credential, create an agent key on your dashboard and enter it in Muse’s secure credential prompt — never paste a key into the chat itself.
• Instinct, and agents with their own computer. Give the agent the connector URL and an agent key — it sends the key as Authorization: Bearer <key>. Agents that work in a web browser can also sign in at seatswiper.com/signin with your email and password and use the dashboard exactly as you would (if you signed up with Google, set a password first with “Forgot password” on the sign-in page).
• Any other MCP client. Point it at the connector URL. Clients that support OAuth discover our sign-in automatically; clients that take a header use an agent key.

With the connector flow, your browser opens a SeatSwiper consent page — sign in if asked, review what the agent will be able to do, and click Allow. With an agent key, there’s no browser step at all.

First time here? You’ll also want the usual SeatSwiper setup — a payment card on file plus the reservation platform for your venue connected. Ask your agent to check your account setup and it will tell you exactly what’s missing.

Headless quick start (for agents and developers)

• Endpoint: https://www.seatswiper.com/api/mcp — MCP over Streamable HTTP. Use the www host exactly; the bare domain redirects, and some clients won’t replay a redirected POST.
• Agent key: send Authorization: Bearer ss_ak_… (or X-API-Key: ss_ak_…). Create keys on the dashboard; each is shown once, valid for a year, and revocable anytime.
• OAuth 2.1: dynamic client registration + PKCE (S256). Discovery: /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. An unauthenticated request returns 401 with a WWW-Authenticate pointer to the metadata.
• Limits: 120 requests a minute per account. A revoked or expired key gets a 401 — create a new one.

curl -s https://www.seatswiper.com/api/mcp \
  -H "Authorization: Bearer $SEATSWIPER_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}'

A machine-readable summary for agents lives at seatswiper.com/llms.txt.

What your agent can do

• Check account setup. Which prerequisites (card, Resy / OpenTable / SevenRooms links) are missing, free bookings remaining, and your active-booking count.
• Search restaurants. Find a venue by name across Resy, SevenRooms, and OpenTable.
• Check when reservations release. When a date "drops" for a venue, and whether SeatSwiper would race the drop or watch for a cancellation.
• Check live availability. Open tables on an already-released date.
• Create a booking. Set up and arm a drop race or cancellation watch — always after confirming the details and the fee with you.
• Arm a draft booking. Arm a saved draft once you have fixed a setup issue (for example, added a card).
• List bookings. Your bookings with their state and latest result.
• List saved Resy cards. The cards on your Resy account, so a booking can charge a specific one.
• Cancel a booking. Cancel by booking id.

Fees

• Same fees as the dashboard, never more. A drop race costs $5 only when SeatSwiper lands your table (nothing on a miss); a cancellation watch costs $1 to start plus the $5 on success. Your first successful booking’s $5 is free.
• We never see your conversations. Our servers receive only the individual requests your agent sends (for example, a restaurant search) — never your chat with it.

Disconnecting

Open the ✦ chip on your dashboard and click Disconnect next to any agent or agent key — access ends immediately. You can also remove the connector in your agent’s own settings. Reconnecting always takes a fresh consent or a new key.

Troubleshooting & support

• The connect flow fails or loops. Sign in to SeatSwiper first at seatswiper.com/signin, then retry the connection. If it still fails, wait a minute and try again.
• Your agent gets “unauthorized” with a key. The key was revoked, expired, or mistyped — create a new one on the dashboard and update your agent’s credential.
• A tool reports a setup problem. Messages like “no payment card on file” or “Resy account not connected” are fixed on your dashboard; the draft booking is saved, and the agent can arm it once you’ve fixed the issue.
• Use the www address. If you paste the connector URL manually, use https://www.seatswiper.com/api/mcp exactly — including the www.
• Anything else — email support@seatswiper.com and we’ll dig in.

See also our Privacy Policy and Terms of Service.