A Hermes subagent monitors Resy and gets its user suspended
Brian Distelburger built a personal agent called Hannah, using Hermes with Obsidian for memory and Telegram as the interface. For date nights in New York, he created a Hermes subagent to watch Resy for openings at restaurants he and his wife liked. Distelburger says the monitor worked so well that it repeatedly checked Resy, but he had not set a rate limit.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Handle this task in the connected browser or phone tools, show me the sources and choices, and pause before confirming any booking, payment or account change.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- Brian Distelburger (@bdistel)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The monitoring found openings but triggered an account suspension. Distelburger says Resy restored the account once as a courtesy; no table booking is reported.
- Human involvement
- Distelburger configured the agent and later handled the support requests. He says he had not realized how frequently it queried Resy.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Distelburger configured a Hermes subagent to monitor Resy for openings at preferred restaurants.
- The subagent polled Resy repeatedly without a configured rate limit.
- After Resy suspended his account, Distelburger contacted support and reports receiving a one-time courtesy reinstatement.
Brian Distelburger built a personal agent called Hannah, using Hermes with Obsidian for memory and Telegram as the interface. For date nights in New York, he created a Hermes subagent to watch Resy for openings at restaurants he and his wife liked. Distelburger says the monitor worked so well that it repeatedly checked Resy, but he had not set a rate limit.
Resy suspended his account and sent a notice saying his activity violated its terms. Distelburger submitted support requests through several channels and says the account was eventually restored as a one-time courtesy. The outcome is a useful failure report: an agent can find openings while still causing trouble if it polls a service too aggressively.
The lesson is operational, not just about reservations. Set a conservative polling interval, use the service’s permitted access methods, cap retries and stop when a site shows a block or warning. Distelburger says he had not realized how frequently the subagent was making requests. His account also shows the human cost: losing access to a long-held Resy account disrupted his usual reservation routine. The post does not claim the agent booked a table, so this page focuses on monitoring and the resulting suspension, not a successful reservation.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · Brian Distelburger (@bdistel)
Frequently asked questions
What was the Hermes subagent supposed to do?
It monitored Resy for openings at restaurants Distelburger and his wife liked for date nights.
What went wrong?
The subagent checked too frequently because Distelburger had not set a rate limit. Resy suspended his account for violating its terms.
Was the account restored?
Distelburger says Resy reinstated it once as a courtesy after he contacted support through several channels.
More details
About this account
The Hermes subagent repeatedly monitored Resy for reservation openings without a rate limit configured by its owner.
Reviewed the archived direct X page capture (HTTP 200, 2026-10-15) for author, post text and publication date; a fresh fetch from the current web reader returned 403. The prompt is editorially suggested because the post does not share an exact instruction.
Credit: Brian Distelburger (@bdistel) — X
Source published
Added to Agents In Use
Source checked
Tools and topics
Hermes Agent · Obsidian · Telegram · Resy
Resy · reservation monitoring · rate limits
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.