Customize and order a matcha drink for an event
You met me at a very agentic time in my life Just got coconut cloud matcha ordered by @MonidHQ agent by my first event of SF tech week: agent matcha rooftop pop up I connected my Monid API keys into my Claude cowork and it let me customize the milk and order for me Excited to try out Monid to…. Task: The user connected Monid API keys to Claude Cowork to automate a beverage order for a tech event. The agent customized the drink (coconut cloud matcha) and placed the order via the Monid service. Human involvement was limited to initial setup and API key integration, with no explicit confirmation step mentioned in the source.; tools: Claude Cowork. Human role: The original post does not say how a person stayed involved.; limitations: Relies on valid Monid API keys and Claude Cowork integration. The source does not specify costs, latency, or failure handling for the ordering process. Human approval steps are not documented, creating a risk of unauthorized or incorrect orders if the agent misinterprets preferences..
Tools
Published on Agent Work Atlas:
Overview
You met me at a very agentic time in my life Just got coconut cloud matcha ordered by @MonidHQ agent by my first event of SF tech week: agent matcha rooftop pop up I connected my Monid API keys into my Claude cowork and it let me customize the milk and order for me Excited to try out Monid to…
Workflow
The user connected Monid API keys to Claude Cowork to automate a beverage order for a tech event. The agent customized the drink (coconut cloud matcha) and placed the order via the Monid service. Human involvement was limited to initial setup and API key integration, with no explicit confirmation step mentioned in the source.
Reported result
The source confirms the order was placed but provides no metrics on cost, delivery time, or error rates. It is unknown if the customization was perfectly executed or if any manual intervention was required post-order. A measurable acceptance check would be verifying the receipt of the specific customized item at the event.
Human role
The original post does not say how a person stayed involved.
Limitations
Relies on valid Monid API keys and Claude Cowork integration. The source does not specify costs, latency, or failure handling for the ordering process. Human approval steps are not documented, creating a risk of unauthorized or incorrect orders if the agent misinterprets preferences.
Try it
I want to automate ordering a specific beverage for an upcoming event using Monid and Claude Cowork. My event is [replaceable: event name/location], and I want to order [replaceable: drink name/customization]. First, verify my Monid API keys are correctly connected to Claude Cowork. Draft the order details including the specific customization. Show me the draft for approval before sending. If approved, execute the order via the Monid agent. Confirm the order status and provide the receipt. If the API connection fails, stop and ask for new keys. Do not spend money without my explicit 'yes' confirmation.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.