Same booking task, two agents: Muse finished, the other was still searching
Alex VolkovX (Twitter) · 2026-09-09
Read originalI gave @muse and Instinct the same task, to research tickets for a rosh-ha-shana dinner. @muse is already tightly integrated with link... and it booked me tickets, while Instinct is still searching for the RSVP!
Business model
In a head-to-head the author ran, Muse took a family holiday-dinner ticket task and completed the booking and payment through its native Link integration - the confirmation shows child tickets and allergy notes - while the competing agent was still searching (author-reported; ticket price undisclosed).
The agent searches, books and pays through its native wallet integration and returns an itemized confirmation; the owner checks child tickets and notes line by line.
Workflow
- Provide the event, party size with children's ages, and special notes.
- The agent finds options and completes booking and payment after your confirmation.
- Check the confirmation line by line.
Adaptation plan
Ticket price is undisclosed. Payment approval should stay on for agent purchases. AgentFlow has not independently deployed this adaptation.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
Book tickets for this event (event and party details attached, including children's ages) and put the allergy information in the notes. Show me the option and total before paying. Afterwards, itemize the confirmation: headcount, child tickets, notes, payment method.
Running costs and pitfalls
Ticket price is undisclosed. Payment approval should stay on for agent purchases. AgentFlow has not independently deployed this adaptation. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.